/* * Shared crypto simd helpers */ #ifndef _CRYPTO_INTERNAL_SIMD_H #define _CRYPTO_INTERNAL_SIMD_H struct simd_skcipher_alg; struct simd_skcipher_alg *simd_skcipher_create_compat(const char *algname, const char *drvname, const char *basename); struct simd_skcipher_alg *simd_skcipher_create(const char *algname, const char *basename); void simd_skcipher_free(struct simd_skcipher_alg *alg); #endif /* _CRYPTO_INTERNAL_SIMD_H */ .ch/linux/net-next.git' title='net-next.git Git repository'/>
summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/i2c
diff options
context:
space:
mode:
authorChao Yu <yuchao0@huawei.com>2016-08-21 23:21:30 +0800
committerJaegeuk Kim <jaegeuk@kernel.org>2016-09-07 17:27:33 -0700
commit74fa5f3d43bca87257e9da7da95be8735ffa2b96 (patch)
treea3d972110c11454cbf7c5964bd49184863d9f229 /Documentation/devicetree/bindings/i2c
parent97c1794a5dc160164aa7f161310da15c34d62641 (diff)
f2fs: schedule in between two continous batch discards
In batch discard approach of fstrim will grab/release gc_mutex lock repeatly, it makes contention of the lock becoming more intensive. So after one batch discards were issued in checkpoint and the lock was released, it's better to do schedule() to increase opportunity of grabbing gc_mutex lock for other competitors. Signed-off-by: Chao Yu <yuchao0@huawei.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'Documentation/devicetree/bindings/i2c')