linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Wolfgang Wander <wwc@rentec.com>
Cc: kenneth.w.chen@intel.com, mingo@elte.hu, arjanv@redhat.com,
	linux-mm@kvack.org
Subject: Re: Fw: [Bug 4520] New: /proc/*/maps fragments too quickly compared to
Date: Tue, 10 May 2005 12:57:47 -0700	[thread overview]
Message-ID: <20050510125747.65b83b4c.akpm@osdl.org> (raw)
In-Reply-To: <17025.4213.255704.748374@gargle.gargle.HOWL>

Wolfgang Wander <wwc@rentec.com> wrote:
>
> Andrew Morton writes:
>  > "Chen, Kenneth W" <kenneth.w.chen@intel.com> wrote:
>  > >
>  > > Andrew Morton wrote Tuesday, May 10, 2005 11:58 AM
>  > > > "Chen, Kenneth W" <kenneth.w.chen@intel.com> wrote:
>  > > > > Andrew Morton wrote on Monday, May 09, 2005 2:27 PM
>  > > > > > Possibly for the 2.6.12 release the safest approach would be to just
>  > > > > > disable the free area cache while we think about it.
>  > > > > 
>  > > > > I hope people are not thinking permanently kill the free area cache
>  > > > > algorithm.  It is known to give a large percentage of performance gain
>  > > > > on specweb SSL benchmark.  I think it gives 4-5% gain from free area
>  > > > > cache algorithm.
>  > > > 
>  > > > It also makes previously-working workloads completely *fail*.
>  > > 
>  > > I agree that functionality over rule most of everything else.  Though, I
>  > > do want to bring to your attention on how much performance regression we
>  > > will see if the free area cache is completely disabled.  I rather make
>  > > noise now instead of a couple month down the road :-)
>  > 
>  > Well we allegedly have a patch from Wolfgang which fixes things up, but our
>  > talk-to-testing ratio seems to be infinite.
>  > 
>  > This is pretty serious, guys.  Could someone please find the time to work
>  > on it?
> 
> I volunteer to do the testing - just the test I got from Ingo did
> not show any timing difference for either of the three solutions:
> 
> a) use free_cache
> b) disable free_cache
> c) use my maybe improved and maybe much too complex free_cache
> 
> The test_str02.c I got only ran up to 1300 threads on my machine (8GB
> dual x86_64) and Ingo expected it to go up to 20000.
> 
> If there is any other test case I'm very willing to do the timing
> tests...
> 

Oh well, I might as well get it into -mm as long as we're (not) thinking
about it.

Could you please send along the latest version, against 2.6.12-rc4, with
description, signed-off-by, etc?

--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2005-05-10 19:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 13:30 Wolfgang Wander
2005-05-09 21:26 ` Andrew Morton
2005-05-09 21:30   ` Arjan van de Ven
2005-05-10 13:23     ` Wolfgang Wander
2005-05-10 15:35   ` Chen, Kenneth W
2005-05-10 18:58     ` Andrew Morton
2005-05-10 19:07       ` Arjan van de Ven
2005-05-10 19:34       ` Chen, Kenneth W
2005-05-10 19:43         ` Andrew Morton
2005-05-10 19:50           ` Wolfgang Wander
2005-05-10 19:57             ` Andrew Morton [this message]
2005-05-11 14:36               ` [PATCH] Avoiding mmap fragmentation (against 2.6.12-rc4) to Wolfgang Wander
2005-05-11 15:05                 ` Chen, Kenneth W
2005-05-12  0:59                 ` Andrew Morton
2005-05-12  1:33                   ` Wolfgang Wander
2005-05-12  7:07                 ` Ingo Molnar
2005-05-12  7:14                 ` Ingo Molnar
2005-05-10 19:58             ` Fw: [Bug 4520] New: /proc/*/maps fragments too quickly compared to Ingo Molnar
2005-05-10 20:04               ` Wolfgang Wander

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=20050510125747.65b83b4c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=wwc@rentec.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