On 03/23, Waiman Long wrote:
> On 3/23/22 12:48, Jaegeuk Kim wrote:
> > On 03/23, Christoph Hellwig wrote:
> > > On Tue, Mar 22, 2022 at 10:22:50AM -0700, Linus Torvalds wrote:
> > > > On Mon, Mar 21, 2022 at 1:39 PM Jaegeuk Kim wrote:
> > > > > In this cycle, f2fs has some performance improvement
On 03/23, Linus Torvalds wrote:
> On Wed, Mar 23, 2022 at 9:26 AM Jaegeuk Kim wrote:
> >
> > OTOH, I was suspecting the major contetion would be
> > f2fs_lock_op -> f2fs_down_read(&sbi->cp_rwsem);
> > , which was used for most of filesystem operations.
>
> Very possible, I was just lookin
On 3/23/22 12:48, Jaegeuk Kim wrote:
On 03/23, Christoph Hellwig wrote:
On Tue, Mar 22, 2022 at 10:22:50AM -0700, Linus Torvalds wrote:
On Mon, Mar 21, 2022 at 1:39 PM Jaegeuk Kim wrote:
In this cycle, f2fs has some performance improvements for Android workloads such
as using read-unfair rwse
On Wed, Mar 23, 2022 at 9:26 AM Jaegeuk Kim wrote:
>
> OTOH, I was suspecting the major contetion would be
> f2fs_lock_op -> f2fs_down_read(&sbi->cp_rwsem);
> , which was used for most of filesystem operations.
Very possible, I was just looking at a random one in f2fs/file.c
obviously wit
On 03/23, Christoph Hellwig wrote:
> On Wed, Mar 23, 2022 at 09:48:17AM -0700, Jaegeuk Kim wrote:
> > Christoph, I proposed,
> >
> > "I've been waiting for a generic solution as suggested here. Until then,
> > I'd like
> > to keep this in f2fs *only* in order to ship the fix in products. Once
>
On Wed, Mar 23, 2022 at 09:48:17AM -0700, Jaegeuk Kim wrote:
> Christoph, I proposed,
>
> "I've been waiting for a generic solution as suggested here. Until then, I'd
> like
> to keep this in f2fs *only* in order to ship the fix in products. Once there's
> a right fix, let me drop or revise this
On 03/23, Christoph Hellwig wrote:
> On Tue, Mar 22, 2022 at 10:22:50AM -0700, Linus Torvalds wrote:
> > On Mon, Mar 21, 2022 at 1:39 PM Jaegeuk Kim wrote:
> > >
> > > In this cycle, f2fs has some performance improvements for Android
> > > workloads such
> > > as using read-unfair rwsems [...]
>
On 03/22, Linus Torvalds wrote:
> On Tue, Mar 22, 2022 at 5:34 PM Tim Murray wrote:
> >
> > AFAICT, what's happening is that rwsem_down_read_slowpath
> > modifies sem->count to indicate that there's a pending reader while
> > f2fs_ckpt holds the write lock, and when f2fs_ckpt releases the write
>
The test fail on f2fs:
xattr names and values after second fsync log replay:
# file: SCRATCH_MNT/foobar
+user.attr1="val1"
user.attr3="val3"
attr1 is still there after log replay. f2fs doesn't support fs-op level
transaction functionality. so it have no way to persist all metada
On Tue, Mar 22, 2022 at 10:22:50AM -0700, Linus Torvalds wrote:
> On Mon, Mar 21, 2022 at 1:39 PM Jaegeuk Kim wrote:
> >
> > In this cycle, f2fs has some performance improvements for Android workloads
> > such
> > as using read-unfair rwsems [...]
>
> I've pulled this, but that read-unfair rwsem
10 matches
Mail list logo
