Re: [git pull] vfs pile 1

2014-01-29 Jan Kara : > On Tue 28-01-14 19:26:08, Linus Torvalds wrote: >> On Mon, Jan 27, 2014 at 6:25 AM, Al Viro wrote: >> > Assorted stuff; the biggest pile here is Christoph's ACL series. >> > Plus assorted cleanups and fixes all over the place... There will be >> > another pile late

Re: [f2fs-dev] [PATCH] f2fs: optimize fs_lock for better performance

Hi Gu, 2013/9/11 Gu Zheng : > Hi Jaegeuk, Chao, > > On 09/10/2013 08:52 AM, Jaegeuk Kim wrote: > >> Hi, >> >> At first, thank you for the report and please follow the email writing >> rules. :) >> >> Anyway, I agree to the below issue. >> One thing that I can think of is that we don't need to use

Re: [f2fs-dev] [PATCH] f2fs: optimize fs_lock for better performance

Hi Russ, The usage of fs_locks is for the recovery, so it doesn't matter with stress-testing. Actually what I've concerned is that we should not grab two or more fs_locks in the same call path. Thanks, 2013/9/11 Russ Knize : > Hi Jaegeuk/Gu, > > I've removed the lock and have been stress-testing

Re: Re: [f2fs-dev][PATCH] f2fs: optimize fs_lock for better performance

Hi, 2013/9/11 Chao Yu > > Hi Kim, > > I did some tests as you mention of using random instead of spin_lock. > The test model is as following: > eight threads race to grab one of eight locks for one thousand times, > and I used four methods to generate lock num: > > 1.atomic_add_return(1, &sbi->ne

Re: [PATCH 00/16 v3] f2fs: introduce flash-friendly file system

2012/11/2 Martin Steigerwald > > Am Mittwoch, 31. Oktober 2012 schrieb Jaegeuk Kim: > > Change log from v2: > > > > o Fix compilation error for arm [Max] > > o Move proc entries to debugfs [Greg] > > o Add i_atime, i_generation, etc [Neil] > > o Support NFS export [Changman] > > o Move the f2