From: Jan Kara <jack@suse.cz>
To: Waiman Long <Waiman.Long@hpe.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.com>, Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andi Kleen <andi@firstfloor.org>,
Dave Chinner <dchinner@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Scott J Norton <scott.norton@hp.com>,
Douglas Hatch <doug.hatch@hp.com>
Subject: Re: [PATCH v5 0/5] vfs: Use per-cpu list for SB's s_inodes list
Date: Thu, 3 Mar 2016 11:41:18 +0100 [thread overview]
Message-ID: <20160303104118.GF2307@quack.suse.cz> (raw)
In-Reply-To: <1456866003-32441-1-git-send-email-Waiman.Long@hpe.com>
On Tue 01-03-16 15:59:58, Waiman Long wrote:
> v4->v5:
> - Fix the UP panic problem reported by 0day test by unifying the SMP
> and UP code.
> - Add patch 5 to add a new kernel config parameter to allow disabling
> per-cpu list for small systems that won't benefit much from this
> feature.
Hum, it seems you've missed my comment in [1] regarding a race I found.
[1] http://www.spinics.net/lists/linux-fsdevel/msg95052.html
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2016-03-03 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 20:59 [PATCH v5 0/5] vfs: Use per-cpu list for SB's s_inodes list Waiman Long
2016-03-01 20:59 ` [PATCH v5 1/5] lib/percpu-list: Per-cpu list with associated per-cpu locks Waiman Long
2016-03-01 21:00 ` [PATCH v5 2/5] fsnotify: Simplify inode iteration on umount Waiman Long
2016-03-01 21:00 ` [PATCH v5 3/5] vfs: Remove unnecessary list_for_each_entry_safe() variants Waiman Long
2016-03-01 21:00 ` [PATCH v5 4/5] vfs: Use per-cpu list for superblock's inode list Waiman Long
2016-03-01 21:00 ` [PATCH v5 5/5] lib/percpu-list: Add a config parameter for disabling per-cpu list Waiman Long
2016-03-02 8:41 ` Ingo Molnar
2016-03-02 21:55 ` Waiman Long
2016-03-03 10:41 ` 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=20160303104118.GF2307@quack.suse.cz \
--to=jack@suse.cz \
--cc=Waiman.Long@hpe.com \
--cc=andi@firstfloor.org \
--cc=bfields@fieldses.org \
--cc=boqun.feng@gmail.com \
--cc=cl@linux-foundation.org \
--cc=dchinner@redhat.com \
--cc=doug.hatch@hp.com \
--cc=jack@suse.com \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=scott.norton@hp.com \
--cc=tj@kernel.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 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.