Dear Friend:
Have a good day!
GoodFortune Promotion Co,Ltd located in china,can supply all kinds of customed
promotion gift.
Even samll order is available,pls check our web,any further inquiry,contact us
feel feel at once.
Best Regards
Paul Lee
ShangHai GoodFortune Gifts Promotion Co.,Ltd
Hi Jaegeuk,
On 07/02/2014 06:30 PM, Jaegeuk Kim wrote:
> Thanks Changman for reminding this. :)
>
> If there are a lot of ones in the bit stream, find_next_bit_le would cause
> some
> overhead to translate the bits.
>
> However, it would be effective to use find_next_bit_le if the bit stream lo
Hi Changman,
On 07/02/2014 03:49 PM, Changman Lee wrote:
> Hi, Gu
>
> Unfortunately, find_next_bit isn't always better than test_bit.
> Refer to commit 5d0c667121bfc8be76d1580f485bddbe73465d1a
>
> I remember that
> Perviously, Jaegeuk had changed find_next_bit to test_bit because
> find_next_bit
On Wed, 2 Jul 2014 02:31:26 -0700 Jaegeuk Kim wrote:
> > > --- a/fs/f2fs/node.c
> > > +++ b/fs/f2fs/node.c
> > > @@ -43,6 +43,8 @@ bool available_free_memory(struct f2fs_sb_info *sbi,
> > > int type)
> > > mem_size = (nm_i->nat_cnt * sizeof(struct nat_entry)) >> 12;
> > > res
If an inode is renamed, it should be registered as file_lost_pino to conduct
checkpoint at f2fs_sync_file.
Otherwise, the inode cannot be recovered due to no dent_mark in the following
scenario.
Note that, this scenario is from xfstests/322.
1. create "a"
2. fsync "a"
3. rename "a" to "b"
4. fsyn
Thanks Changman for reminding this. :)
If there are a lot of ones in the bit stream, find_next_bit_le would cause some
overhead to translate the bits.
However, it would be effective to use find_next_bit_le if the bit stream looks
like 01.
Well, IMO the former case would be a little bit m
On Tue, Jul 01, 2014 at 10:54:20PM -0700, Andrew Morton wrote:
> On Sat, 28 Jun 2014 20:58:38 +0900 Jaegeuk Kim wrote:
>
> > If we don't check the current backing device status, balance_dirty_pages can
> > fall into infinite pausing routine.
> >
> > This can be occurred when a lot of directories
Hi, Gu
Unfortunately, find_next_bit isn't always better than test_bit.
Refer to commit 5d0c667121bfc8be76d1580f485bddbe73465d1a
I remember that
Perviously, Jaegeuk had changed find_next_bit to test_bit because
find_next_bit spent much cpu time in the case of there is lot of dentries like
a postm
