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

2013-09-09 Thread Jaegeuk Kim
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 the spin_lock, since we don't care about the exact lock number, but just need to get any not-collided number. So,

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

2013-09-09 Thread Russ Knize
I wasn't sure if f2fs_setxattr() needed the lock or not, since the call path from f2fs_xattr_set_acl() doesn't take one anywhere. My first thought was to move the lock over to the acl code and remove it from here. Russ On Mon, Sep 9, 2013 at 7:59 PM, Jaegeuk Kim jaegeuk@samsung.com wrote: