[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f11576a0808130805s6963e2a4mbb82ad7221cf80a2@mail.gmail.com>
Date: Thu, 14 Aug 2008 00:05:54 +0900
From: "KOSAKI Motohiro" <kosaki.motohiro@...fujitsu.com>
To: "Christoph Lameter" <cl@...ux-foundation.org>
Cc: "Matthew Wilcox" <matthew@....cx>,
"Pekka Enberg" <penberg@...helsinki.fi>, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
"Mel Gorman" <mel@...net.ie>, andi@...stfloor.org,
"Rik van Riel" <riel@...hat.com>
Subject: Re: No, really, stop trying to delete slab until you've finished making slub perform as well
> Yes but running with this patch would allow us to verify that we understand
> what is causing the problem. There are other solutions like skipping to the
> next partial slab on the list that could fix performance issues that the patch
> may cause. A test will give us:
>
> 1. Confirmation that the memory use is caused by the trylock.
>
> 2. Some performance numbers. If these show a regression then we have some
> markers that we can measure other solutions against.
okey.
I will confirm its patch at next week.
(unfortunately, my company don't business in rest this week)
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists