From: Geliang Tang <geliangtang@163.com>
To: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Geliang Tang <geliangtang@163.com>
Subject: Re: [PATCH v2] mm/slab.c: use list_{empty_careful,last_entry} in drain_freelist
Date: Sat, 5 Dec 2015 10:36:27 +0800 [thread overview]
Message-ID: <20151205023627.GA9812@bogon> (raw)
In-Reply-To: <alpine.DEB.2.20.1512041014440.21427@east.gentwo.org>
On Fri, Dec 04, 2015 at 10:16:38AM -0600, Christoph Lameter wrote:
> On Fri, 4 Dec 2015, Geliang Tang wrote:
>
> > On Thu, Dec 03, 2015 at 08:53:21AM -0600, Christoph Lameter wrote:
> > > On Thu, 3 Dec 2015, Geliang Tang wrote:
> > >
> > > > while (nr_freed < tofree && !list_empty(&n->slabs_free)) {
> > > >
> > > > spin_lock_irq(&n->list_lock);
> > > > - p = n->slabs_free.prev;
> > > > - if (p == &n->slabs_free) {
> > > > + if (list_empty_careful(&n->slabs_free)) {
> > >
> > > We have taken the lock. Why do we need to be "careful"? list_empty()
> > > shoudl work right?
> >
> > Yes. list_empty() is OK.
> >
> > >
> > > > spin_unlock_irq(&n->list_lock);
> > > > goto out;
> > > > }
> > > >
> > > > - page = list_entry(p, struct page, lru);
> > > > + page = list_last_entry(&n->slabs_free, struct page, lru);
> > >
> > > last???
> >
> > The original code delete the page from the tail of slabs_free list.
>
> Maybe make the code clearer by using another method to get the page
> pointer?
>
> > >
> > > Would the the other new function that returns NULL on the empty list or
> > > the pointer not be useful here too and save some code?
> >
> > Sorry, I don't really understand what do you mean. Can you please specify
> > it a little bit?
>
> I take that back. list_empty is the best choice here.
If we use list_empty(), there will be two list_empty() in the code:
while (nr_freed < tofree && !list_empty(&n->slabs_free)) {
spin_lock_irq(&n->list_lock);
if (list_empty(&n->slabs_free)) {
spin_unlock_irq(&n->list_lock);
goto out;
}
page = list_last_entry(&n->slabs_free, struct page, lru);
list_del(&page->lru);
spin_unlock_irq(&n->list_lock);
}
Or can we drop the first list_empty() like this? It will function the same as the above code.
while (nr_freed < tofree) {
spin_lock_irq(&n->list_lock);
if (list_empty(&n->slabs_free)) {
spin_unlock_irq(&n->list_lock);
goto out;
}
page = list_last_entry(&n->slabs_free, struct page, lru);
list_del(&page->lru);
spin_unlock_irq(&n->list_lock);
}
Please let me know which one is better?
Thanks.
- Geliang
--
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:[~2015-12-05 2:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 15:46 [PATCH 1/3] mm/slab: use list_first_entry_or_null() Geliang Tang
2015-12-02 15:46 ` [PATCH 2/3] mm/slab: use list_for_each_entry in cache_flusharray Geliang Tang
2015-12-02 15:46 ` [PATCH 3/3] mm/slab: use list_{empty_careful,last_entry} in drain_freelist Geliang Tang
2015-12-02 16:06 ` Christoph Lameter
2015-12-03 14:07 ` [PATCH v2] mm/slab.c: " Geliang Tang
2015-12-03 14:53 ` Christoph Lameter
2015-12-04 13:43 ` Geliang Tang
2015-12-04 16:16 ` Christoph Lameter
2015-12-05 2:36 ` Geliang Tang [this message]
2015-12-02 15:58 ` [PATCH 2/3] mm/slab: use list_for_each_entry in cache_flusharray Christoph Lameter
2015-12-02 15:57 ` [PATCH 1/3] mm/slab: use list_first_entry_or_null() 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=20151205023627.GA9812@bogon \
--to=geliangtang@163.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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