All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@google.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, Andreas Gruenbacher <agruenba@redhat.com>
Subject: Re: [PATCH 1/5] mbcache: correctly handle 'e_referenced' bit
Date: Mon, 28 Nov 2016 09:32:43 -0800	[thread overview]
Message-ID: <20161128173243.GA137838@google.com> (raw)
In-Reply-To: <20161128104420.GF2590@quack2.suse.cz>

On Mon, Nov 28, 2016 at 11:44:20AM +0100, Jan Kara wrote:
> On Sat 26-11-16 22:17:57, Eric Biggers wrote:
> > mbcache entries have an 'e_referenced' bit which users can set with
> > mb_cache_entry_touch() to indicate that an entry should be given another
> > pass through the LRU list before the shrinker can delete it.  However,
> > mb_cache_shrink() actually would, when seeing an e_referenced entry at
> > the front of the list (the least-recently used end), place it right at
> > the front of the list again.  The next iteration would then remove the
> > entry from the list and delete it.  Consequently, e_referenced had
> > essentially no effect, so ext2/ext4 xattr blocks would sometimes not be
> > reused as often as expected.
> > 
> > Fix this by making the shrinker move e_referenced entries to the back of
> > the list rather than the front.
> > 
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
> 
> Bah, good spotting. You can add:
> 
> Reviewed-by: Jan Kara <jack@suse.cz>
> 
> BTW, how did you find out?
> 

Nothing special --- I just happened to notice while reading over the code.

Eric

  reply	other threads:[~2016-11-28 17:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27  6:17 [PATCH 1/5] mbcache: correctly handle 'e_referenced' bit Eric Biggers
2016-11-27  6:17 ` [PATCH 2/5] mbcache: don't BUG() if entry cache cannot be allocated Eric Biggers
2016-11-28 12:09   ` Jan Kara
2016-12-03 20:30   ` Theodore Ts'o
2016-11-27  6:17 ` [PATCH 3/5] mbcache: remove unnecessary module_get/module_put Eric Biggers
2016-11-28 13:12   ` Jan Kara
2016-12-03 20:41   ` Theodore Ts'o
2016-11-27  6:18 ` [PATCH 4/5] mbcache: use consistent type for entry count Eric Biggers
2016-11-28 13:18   ` Jan Kara
2016-12-03 20:54   ` Theodore Ts'o
2016-11-27  6:18 ` [PATCH 5/5] mbcache: document that "find" functions only return reusable entries Eric Biggers
2016-11-28 13:19   ` Jan Kara
2016-12-03 20:56   ` Theodore Ts'o
2016-11-28 10:44 ` [PATCH 1/5] mbcache: correctly handle 'e_referenced' bit Jan Kara
2016-11-28 17:32   ` Eric Biggers [this message]
2016-12-03 20:28 ` Theodore Ts'o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161128173243.GA137838@google.com \
    --to=ebiggers@google.com \
    --cc=agruenba@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.