From: Al Viro <viro@ZenIV.linux.org.uk>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Dave Chinner <david@fromorbit.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Jan Kara <jack@suse.cz>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/8] change sb_writers to use percpu_rw_semaphore
Date: Sat, 15 Aug 2015 08:17:00 +0100 [thread overview]
Message-ID: <20150815071700.GH14139@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20150814171935.GA15042@redhat.com>
On Fri, Aug 14, 2015 at 07:19:35PM +0200, Oleg Nesterov wrote:
> On 08/13, Jan Kara wrote:
> >
> > Regarding the routing, ideally Al Viro should take these as a VFS
> > maintainer.
>
> Al, could you take these patches?
I can live with that. Do you have it as a branch in a public git tree?
next prev parent reply other threads:[~2015-08-15 7:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 17:19 [PATCH v3 0/8] change sb_writers to use percpu_rw_semaphore Oleg Nesterov
2015-08-14 17:19 ` [PATCH v3 1/8] introduce __sb_writers_{acquired,release}() helpers Oleg Nesterov
2015-08-14 17:19 ` [PATCH v3 2/8] fix the broken lockdep logic in __sb_start_write() Oleg Nesterov
2015-08-14 17:19 ` [PATCH v3 3/8] document rwsem_release() in sb_wait_write() Oleg Nesterov
2015-08-14 17:19 ` [PATCH v3 4/8] percpu-rwsem: introduce percpu_down_read_trylock() Oleg Nesterov
2015-08-14 17:20 ` [PATCH v3 5/8] percpu-rwsem: introduce percpu_rwsem_release() and percpu_rwsem_acquire() Oleg Nesterov
2015-08-14 17:20 ` [PATCH v3 6/8] percpu-rwsem: kill CONFIG_PERCPU_RWSEM Oleg Nesterov
2015-08-14 17:20 ` [PATCH v3 7/8] shift percpu_counter_destroy() into destroy_super_work() Oleg Nesterov
2015-08-14 17:20 ` [PATCH v3 8/8] change sb_writers to use percpu_rw_semaphore Oleg Nesterov
2015-08-15 7:17 ` Al Viro [this message]
2015-08-15 12:03 ` [PATCH v3 0/8] " Oleg Nesterov
2015-08-16 13:47 ` Arthur Marsh
2015-08-17 11:35 ` Oleg Nesterov
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=20150815071700.GH14139@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dave.hansen@linux.intel.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).