Dear Sir,
Good day!
Glad to learn that you're in need for teflon/PTFE thread. We are specializing
in this field for 15 years, with good quality and pretty competitive price.
Let's talk details.
Awaiting your early reply.
Tksbr,
Louis
Ningbo Samreal Chemical Co.,Ltd
Add:Room 1603 No.1498
If an amount of data are allocated though fallocate and user writes a couple of
data among the space, f2fs should return the data offset made by user when
SEEK_DATA is requested.
For example, (N: NEW_ADDR by fallocate, X: NEW_ADDR by user)
1) fallocate 0 ~ 10MB
f - N N N N N N N N N N N N ... N
We should set the error number correctly when we fail in recover_dentry(), so
the recover flow could stop for the reason as error number shows instead of
continuing.
Signed-off-by: Chao Yu chao2...@samsung.com
---
fs/f2fs/recovery.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
We have no so such readahead mechanism in -iterate() path as the one in
-read() path, it cause low performance when we read large directory.
This patch add readahead in f2fs_readdir() for better performance.
Signed-off-by: Chao Yu chao2...@samsung.com
---
fs/f2fs/dir.c |6 ++
Previous we do not truncate inline data in inode page when setattr, so following
case could still read the inline data which has already truncated:
1.write inline data
2.ftruncate size to 0
3.ftruncate size to max inline data size
4.read from offset 0
This patch introduces truncate_inline_data()
Dear Sir,
How are you doing?
Need Disposable Nonwoven Wipes,Dupont's Sontara,Kimberly Clark Wypall Wipers?We
are a professional factory of Industrial Wipes,Cleanroom Wipes,Food Service
Wipe in China They are very popular in your market.If you would like to know
more about our products,pls
Previous we do not truncate inline data in inode page when setattr, so following
case could still read the inline data which has already truncated:
1.write inline data
2.ftruncate size to 0
3.ftruncate size to max inline data size
4.read from offset 0
This patch introduces truncate_inline_data()
