From: Christoph Lameter <cl@linux.com>
To: Josh Cartwright <joshc@codeaurora.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
linux-mm@kvack.org
Subject: Re: [PATCH -next] slub: Replace __this_cpu_inc usage w/ SLUB_STATS
Date: Fri, 7 Mar 2014 11:09:34 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.10.1403071108310.21846@nuc> (raw)
In-Reply-To: <20140306182941.GH18529@joshc.qualcomm.com>
On Thu, 6 Mar 2014, Josh Cartwright wrote:
> Although, I'm wondering how exact these statistics need to be. Is
> making them preemption safe even a concern?
Not sure about that. You solution makes it preempt safe. If is can be
tolerated that its racy then raw_cpu_inc() could be used.
--
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>
next prev parent reply other threads:[~2014-03-07 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140306194821.3715d0b6212cc10415374a68@canb.auug.org.au>
[not found] ` <20140306155316.GG18529@joshc.qualcomm.com>
2014-03-06 18:29 ` Josh Cartwright
2014-03-07 17:09 ` Christoph Lameter [this message]
2014-04-14 13:34 ` Johannes Hirte
2014-04-14 13:59 ` Christoph Lameter
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=alpine.DEB.2.10.1403071108310.21846@nuc \
--to=cl@linux.com \
--cc=joshc@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=sfr@canb.auug.org.au \
/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