[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOJsxLH7w_qvMofLD3sNuWpyJ0FO8CNHVnYo03TvY46R2qryog@mail.gmail.com>
Date: Fri, 2 Nov 2012 10:30:06 +0200
From: Pekka Enberg <penberg@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Glauber Costa <glommer@...allels.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, kamezawa.hiroyu@...fujitsu.com,
Johannes Weiner <hannes@...xchg.org>,
Tejun Heo <tj@...nel.org>, Michal Hocko <mhocko@...e.cz>,
Christoph Lameter <cl@...ux.com>,
David Rientjes <rientjes@...gle.com>
Subject: Re: [PATCH v6 00/29] kmem controller for memcg.
On Fri, Nov 2, 2012 at 2:04 AM, Andrew Morton <akpm@...ux-foundation.org> wrote:
> One thing:
>
>> Numbers can be found at https://lkml.org/lkml/2012/9/13/239
>
> You claim in the above that the fork worload is 'slab intensive". Or
> at least, you seem to - it's a bit fuzzy.
>
> But how slab intensive is it, really?
>
> What is extremely slab intensive is networking. The networking guys
> are very sensitive to slab performance. If this hasn't already been
> done, could you please determine what impact this has upon networking?
> I expect Eric Dumazet, Dave Miller and Tom Herbert could suggest
> testing approaches.
IIRC, networking guys have reduced their dependency on slab
performance recently.
Few simple benchmarks to run are hackbench, netperf, and Christoph's
famous microbenchmarks. The sad reality is that you usually have to
wait for few release cycles before people notice that you've destroyed
performance of their favourite workload. :-/
--
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