From: Jan Kara <jack@suse.cz>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
Al Viro <viro@ZenIV.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <dchinner@redhat.com>, Josef Bacik <jbacik@fb.com>,
Jan Kara <jack@suse.cz>,
Holger Hoffstatte <holger@applied-asynchrony.com>
Subject: Re: [PATCH v8 0/2] improve sync efficiency with sb inode wb list
Date: Wed, 22 Jun 2016 15:12:49 +0200 [thread overview]
Message-ID: <20160622131249.GE16492@quack2.suse.cz> (raw)
In-Reply-To: <1466594593-6757-1-git-send-email-bfoster@redhat.com>
On Wed 22-06-16 07:23:11, Brian Foster wrote:
> This is just a rebase to linus' latest master. I haven't heard any
> feedback on this one so Jan suggested I send to a wider audience.
Yeah. Brian is sending these patches for a few months and they get ignored.
Andrew, can you please pick them up if Al doesn't? Thanks!
Honza
> v8:
> - Rebased to latest master.
> - Added Holger's Tested-by.
> v7: http://marc.info/?l=linux-fsdevel&m=145349651407631&w=2
> - Updated patch 1/2 commit log description to reference performance
> impact.
> v6: http://marc.info/?l=linux-fsdevel&m=145322635828644&w=2
> - Use rcu locking instead of s_inode_list_lock spinlock in
> wait_sb_inodes().
> - Refactor wait_sb_inodes() to keep inode on wb list.
> - Drop remaining, unnecessary lazy list removal bits and relocate inode
> list check to clear_inode().
> - Fix up some comments, etc.
> v5: http://marc.info/?l=linux-fsdevel&m=145262374402798&w=2
> - Converted from per-bdi list to per-sb list. Also marked as RFC and
> dropped testing/review tags.
> - Updated to use new irq-safe lock for wb list.
> - Dropped lazy list removal. Inodes are removed when the mapping is
> cleared of the writeback tag.
> - Tweaked wait_sb_inodes() to remove deferred iput(), other cleanups.
> - Added wb list tracepoint patch.
> v4: http://marc.info/?l=linux-fsdevel&m=143511628828000&w=2
>
> Brian Foster (1):
> wb: inode writeback list tracking tracepoints
>
> Dave Chinner (1):
> sb: add a new writeback list for sync
>
> fs/fs-writeback.c | 111 ++++++++++++++++++++++++++++++---------
> fs/inode.c | 2 +
> fs/super.c | 2 +
> include/linux/fs.h | 4 ++
> include/linux/writeback.h | 3 ++
> include/trace/events/writeback.h | 22 ++++++--
> mm/page-writeback.c | 18 +++++++
> 7 files changed, 133 insertions(+), 29 deletions(-)
>
> --
> 2.5.5
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-06-22 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 11:23 [PATCH v8 0/2] improve sync efficiency with sb inode wb list Brian Foster
2016-06-22 11:23 ` [PATCH v8 1/2] sb: add a new writeback list for sync Brian Foster
2016-06-22 12:46 ` Holger Hoffstätte
2016-06-22 11:23 ` [PATCH v8 2/2] wb: inode writeback list tracking tracepoints Brian Foster
2016-06-22 13:12 ` Jan Kara [this message]
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=20160622131249.GE16492@quack2.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=bfoster@redhat.com \
--cc=dchinner@redhat.com \
--cc=holger@applied-asynchrony.com \
--cc=jbacik@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@ZenIV.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox