From: Andi Kleen <andi@firstfloor.org>
To: Waiman Long <Waiman.Long@hpe.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Scott J Norton <scott.norton@hp.com>,
Douglas Hatch <doug.hatch@hp.com>
Subject: Re: [RFC PATCH 2/3] lib/list_batch, x86: Enable list insertion/deletion batching in x86-64
Date: Tue, 26 Jan 2016 13:44:13 -0800 [thread overview]
Message-ID: <87vb6gc8ya.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <1453824219-51437-3-git-send-email-Waiman.Long@hpe.com> (Waiman Long's message of "Tue, 26 Jan 2016 11:03:38 -0500")
Waiman Long <Waiman.Long@hpe.com> writes:
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 330e738..443e41d 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -42,6 +42,7 @@ config X86
> select ARCH_SUPPORTS_NUMA_BALANCING if X86_64
> select ARCH_USE_BUILTIN_BSWAP
> select ARCH_USE_CMPXCHG_LOCKREF if X86_64
> + select ARCH_USE_LIST_BATCHING if X86_64
I would make it unconditional. The code is simple enough
and shouldn't have drawbacks on smaller systems.
-Andi
next prev parent reply other threads:[~2016-01-26 21:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 16:03 [RFC PATCH 0/3] lib/list_batch: A simple list insertion/deletion batching facility Waiman Long
2016-01-26 16:03 ` [RFC PATCH 1/3] " Waiman Long
2016-01-27 16:34 ` Peter Zijlstra
2016-01-27 20:22 ` Waiman Long
2016-01-27 20:54 ` Peter Zijlstra
2016-01-28 16:45 ` Waiman Long
2016-01-28 18:35 ` Peter Zijlstra
2016-01-26 16:03 ` [RFC PATCH 2/3] lib/list_batch, x86: Enable list insertion/deletion batching in x86-64 Waiman Long
2016-01-26 21:44 ` Andi Kleen [this message]
2016-01-27 16:38 ` Peter Zijlstra
2016-01-27 20:34 ` Waiman Long
2016-01-26 16:03 ` [RFC PATCH 3/3] vfs: Enable list batching for the superblock's inode list Waiman Long
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=87vb6gc8ya.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=Waiman.Long@hpe.com \
--cc=doug.hatch@hp.com \
--cc=hpa@zytor.com \
--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=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox