From: Christoph Lameter <cl@gentwo.org>
To: "Alex,Shi" <alex.shi@intel.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Chen, Tim C" <tim.c.chen@intel.com>,
"Huang, Ying" <ying.huang@intel.com>
Subject: RE: [PATCH] slub: remove a minus instruction in get_partial_node
Date: Mon, 10 Oct 2011 12:11:42 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1110101210110.16264@router.home> (raw)
In-Reply-To: <1318042113.27949.97.camel@debian>
On Sat, 8 Oct 2011, Alex,Shi wrote:
> On Mon, 2011-10-03 at 21:55 +0800, Christoph Lameter wrote:
> > On Sun, 2 Oct 2011, Shi, Alex wrote:
> >
> > > > A slab on the partial lists always has objects available. Why would it be
> > > > zero?
> > >
> > > Um, my mistaken. The reason should be: if code is here, the slab will be per cpu slab.
> > > It is no chance to be in per cpu partial and no relationship with per cpu partial. So
> > > no reason to use this value as a criteria for filling per cpu partial.
> >
> > I am not sure I understand you. The point of the code is to count the
> > objects available in the per cpu partial pages so that we can limit the
> > number of pages we fetch from the per node partial list.
>
> Maybe my understanding is incorrect for PCP. :)
> What I thought is: when object == null, the page we got from node
> partial list will be added into cpu slab. It has no chance to become per
> cpu partial page. And it has no relationship with further per cpu
> partial count checking. Since even 'available > cpu_partial/2', it
> doesn't mean per cpu partial objects number > cpu_partial/2.
acquire_slab should not return NULL unless something seriously goes wrong.
I think we can remove the]
if (!t)
statement to avoid futher confusion?
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-10-10 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 10:05 Alex,Shi
2011-09-29 14:18 ` Christoph Lameter
2011-10-02 12:55 ` Shi, Alex
2011-10-03 13:55 ` Christoph Lameter
2011-10-08 2:48 ` Alex,Shi
2011-10-10 17:11 ` Christoph Lameter [this message]
2011-10-11 9:50 ` Alex,Shi
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.00.1110101210110.16264@router.home \
--to=cl@gentwo.org \
--cc=alex.shi@intel.com \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
--cc=tim.c.chen@intel.com \
--cc=ying.huang@intel.com \
/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