Hi Chao,
On Wed, Jul 02, 2014 at 01:23:47PM +0800, Chao Yu wrote:
> We assume that modification of some special application could result in zeroed
> name_len, or it is consciously made by somebody. We will deadloop in
> find_in_block when name_len of dir entry is zero.
Could you explain this a li
To Changman,
Just for sure, can you reproduce this issue in the x86 machine with proper
benchmarks? (i.e., test_bit_le vs. find_next_bit_le)
To all,
I cautiously suspect that the performances might be different when processing
f2fs_find_entry, since L1/L2 cache misses due to the intermediate rou
Hi friend,
How are you doing?
We are a professional factory of Industrial Wipes,Disposable Wipes,Cleanroom
Wipes,Food Service Wipes in China .They are very popular in your market.For
more information,pls send us your need to i...@spunlace-nonwovens.com
directly,or pls browse our Alibaba Golden
Hi Yu,
Thanks.
On 07/04/2014 02:21 PM, Chao Yu wrote:
> Hi Jaegeuk, Gu, Changman
>
>> -Original Message-
>> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
>> Sent: Friday, July 04, 2014 1:36 PM
>> To: Gu Zheng
>> Cc: f2fs; fsdevel; 이창만; 俞
>> Subject: Re: [PATCH 3/4] f2fs: use find_next_bit