public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3-mm3
Date: Mon, 23 Feb 2004 13:02:49 +1100	[thread overview]
Message-ID: <40395F49.1010702@cyberone.com.au> (raw)
In-Reply-To: <20040222175507.558a5b3d.akpm@osdl.org>



Andrew Morton wrote:

>Nick Piggin <piggin@cyberone.com.au> wrote:
>
>>
>>
>>Andrew Morton wrote:
>>
>>
>>>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm2/
>>>
>>>
>>>
>>URL is of course,
>>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm3/
>>
>
>Yes, thanks.
>
>
>>This still doesn't shrink slab correctly on highmem machines
>>because you dropped my patch :(
>>
>
>First, one needs to define "correctly".
>
>Certainly, it is not "solves the alleged updatedb problem".
>
>

No, I think this is a non-problem.

>The design behind the slab shrinking is to reclaim slab in response to
>memory demand.  Not in response to lowmem demand.  With all the scaling,
>accounting-for-seeks-and-locality, etc.
>
>

That should come out in the wash with my patch anyway, because
it causes lowmem LRU pressure to assert a *lot* more slab pressure.
So highmem pressure should cause a similar amount of slab pressure
with either patch, it just comes about in different ways.

But allocations from lowmem will not shrink the slab nearly enough
with your patch because it shrinks by a percent of all pages.


  reply	other threads:[~2004-02-23  2:02 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23  1:22 2.6.3-mm3 Andrew Morton
2004-02-23  1:43 ` 2.6.3-mm3 Nick Piggin
2004-02-23  1:55   ` 2.6.3-mm3 Andrew Morton
2004-02-23  2:02     ` Nick Piggin [this message]
2004-02-23  2:51     ` 2.6.3-mm3 Nick Piggin
2004-02-23  3:04       ` 2.6.3-mm3 Nick Piggin
2004-02-23  8:08         ` 2.6.3-mm3 Nick Piggin
2004-02-23  8:48           ` [PATCH] vm-fix-all_zones_ok (was Re: 2.6.3-mm3) Nick Piggin
2004-02-23  8:59             ` Andrew Morton
2004-02-23  9:21               ` Nick Piggin
2004-02-23  9:24                 ` Andrew Morton
2004-02-23 16:23                 ` Bill Davidsen
2004-02-23 22:47               ` Chris Wedgwood
2004-02-24  4:11                 ` Nick Piggin
2004-02-24  9:12                   ` Chris Wedgwood
2004-02-24  9:22                     ` Andrew Morton
2004-02-24  9:30                       ` Chris Wedgwood
2004-02-24  9:37                         ` Andrew Morton
2004-02-24 20:55                       ` Rik van Riel
2004-02-24 22:36                         ` Andrew Morton
2004-02-24 22:41                           ` Rik van Riel
2004-02-23  2:19 ` 2.6.3-mm3 Christoph Hellwig
2004-02-23  2:52 ` 2.6.3-mm3 Joshua Kwan
2004-02-23  3:34 ` 2.6.3-mm3 Joshua Kwan
2004-02-23 18:09 ` [patch] 2.6.3-mm3: ALSA miXart driver doesn't compile Adrian Bunk
2004-02-23 18:58 ` 2.6.3-mm3 (compile stats) John Cherry
2004-02-23 20:00   ` Sam Ravnborg
2004-02-24 22:22 ` 2.6.3-mm3 Mike Fedyk
2004-02-24 22:30   ` 2.6.3-mm3 Andrew Morton
2004-02-25 21:27     ` 2.6.3-mm3 Mike Fedyk
2004-02-26  1:06       ` 2.6.3-mm3 Nick Piggin
2004-02-26  1:18         ` 2.6.3-mm3 Marc-Christian Petersen
2004-02-26  1:28           ` 2.6.3-mm3 Mike Fedyk
2004-02-26  1:32         ` 2.6.3-mm3 Mike Fedyk
2004-02-26  1:52           ` 2.6.3-mm3 Nick Piggin
2004-02-26  2:34             ` 2.6.3-mm3 Mike Fedyk
2004-02-26  2:40               ` 2.6.3-mm3 Nick Piggin
2004-02-26  2:48                 ` 2.6.3-mm3 Mike Fedyk
2004-02-26  3:05                   ` 2.6.3-mm3 Nick Piggin
2004-02-26  3:19                     ` 2.6.3-mm3 Mike Fedyk
2004-02-26  3:29                       ` 2.6.3-mm3 Nick Piggin
2004-02-26  4:08                         ` 2.6.3-mm3 Mike Fedyk
2004-02-26  4:56             ` 2.6.3-mm3 Mike Fedyk
2004-02-27 19:02               ` 2.6.3-mm3 Mike Fedyk
2004-02-27 21:57                 ` 2.6.3-mm3 Nick Piggin
2004-02-25  0:26 ` 2.6.3-mm3 hangs on boot x440 (scsi?) john stultz
2004-02-25  1:06   ` Andrew Morton
2004-02-25  1:22     ` john stultz
2004-02-25  1:27       ` john stultz
2004-02-25  1:48       ` Andrew Morton
2004-02-25 22:15         ` john stultz
2004-02-26 14:40     ` Go Taniguchi
2004-02-26 21:26       ` john stultz
2004-02-26 23:02         ` john stultz
2004-02-26 23:15           ` Matthew Wilcox
2004-02-27  0:14             ` john stultz
2004-02-27  0:58               ` john stultz
2004-02-27  2:25             ` john stultz
2004-02-25  1:15 ` [PATCH 2.6.3-mm3] serialize_writeback_fdatawait patch Daniel McNeil
2004-02-25  1:43   ` Andrew Morton
2004-02-25 22:56     ` Daniel McNeil
2004-02-25  2:51 ` 2.6.3-mm3 Mike Fedyk
2004-02-25  3:09   ` 2.6.3-mm3 Andrew Morton
2004-02-25  3:34     ` 2.6.3-mm3 Mike Fedyk
2004-02-25 10:47 ` 2.6.3-mm3 sometimes freeze on "sync" Helge Hafting
2004-02-25  9:39   ` Andrew Morton
2004-02-26  8:49     ` Helge Hafting
2004-02-27 14:49       ` Alexander Hoogerhuis
2004-02-27 23:34 ` 2.6.3-mm3 john stultz
2004-02-28  0:06   ` 2.6.3-mm3 Andrew Morton
2004-02-28  2:48     ` 2.6.3-mm3 (ioremap failure w/ _X86_4G and _NUMA) john stultz
2004-02-28  3:18       ` Dave Hansen
2004-02-28  4:34       ` Martin J. Bligh

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=40395F49.1010702@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /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