From: Linus Torvalds <torvalds@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Mel Gorman <mel@csn.ul.ie>,
Alexander Beregalov <a.beregalov@gmail.com>,
kernel-testers@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Lee Schermerhorn <lee.schermerhorn@hp.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hugh Dickins <hugh@veritas.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@linux-foundation.org>,
bfields@fieldses.org, neilb@suse.de, linux-nfs@vger.kernel.org
Subject: Re: 2.6.26-rc: nfsd hangs for a few sec
Date: Sat, 21 Jun 2008 16:54:47 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0806211651210.2926@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0806211636090.18642@schroedinger.engr.sgi.com>
On Sat, 21 Jun 2008, Christoph Lameter wrote:
>
> Not a direct explanation for the problem but the memory wastage could
> certainly can heretofore undiscovered locking dependencies to be
> exposed.
Well, not for these traces, no. The trace contains __slab_alloc() in the
call chain, which definitely fingers SLUB, not slab, despite the name
(slab calls its allocation routines "cache_alloc", while slub calls them
"slab_alloc" ;)
So the patch looks fine, and I applied it, but as Mel already mentioned,
it looks like it won't be making any difference for Alexander.
Linus
--
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:[~2008-06-21 23:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 12:57 Alexander Beregalov
2008-06-21 18:36 ` Linus Torvalds
2008-06-21 22:41 ` Mel Gorman
2008-06-21 23:46 ` Christoph Lameter
2008-06-21 23:54 ` Linus Torvalds [this message]
2008-06-22 0:18 ` Christoph Lameter
2008-06-22 1:38 ` Mel Gorman
2008-06-22 4:13 ` Christoph Lameter
2008-06-22 17:07 ` Mel Gorman
2008-06-22 2:10 ` Alexander Beregalov
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.LFD.1.10.0806211651210.2926@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=a.beregalov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kernel-testers@vger.kernel.org \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=neilb@suse.de \
--cc=nickpiggin@yahoo.com.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