From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Manfred Spraul <manfred@colorfullife.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] patch-slab-split-03-tail
Date: Fri, 04 Oct 2002 12:15:06 -0700 [thread overview]
Message-ID: <3D9DE8BA.D30EA433@digeo.com> (raw)
In-Reply-To: 1121907497.1033733278@[10.10.2.3]
"Martin J. Bligh" wrote:
>
> > Run that by me again? So we're saying "if we just freed an
> > object from this page then make this page be the *last* page
> > which is eligible for new allocations"? Under the assumption
> > that other objects in that same page are about to be freed
> > up as well?
> >
> > Makes sense. It would be nice to get this confirmed in
> > targetted testing ;)
>
> Just doing my normal boring kernel compile suggest Manfred's
> last big rollup performs exactly the same as without it. Not
> sure if that's any help or not ....
>
Well. This patch is supposed to decrease internal fragmentation.
We need to prove that theory. An appropriate test would be:
- boot with `mem=48m'
- untar kernel
- build kernel
- capture /proc/slabinfo
- apply patch
- repeat
- compare and explain.
I know what your reboot times are like ;) I'll do it.
next prev parent reply other threads:[~2002-10-04 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 17:04 [PATCH] patch-slab-split-03-tail Manfred Spraul
2002-10-04 19:06 ` Andrew Morton
2002-10-04 19:07 ` Martin J. Bligh
2002-10-04 19:15 ` Andrew Morton [this message]
2002-10-04 19:15 ` Manfred Spraul
2002-10-04 20:22 ` Randy.Dunlap
2002-10-04 21:25 ` Manfred Spraul
2002-10-04 21:43 ` Robert Love
2002-10-04 22:30 ` Manfred Spraul
2002-10-05 0:14 ` Anton Blanchard
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=3D9DE8BA.D30EA433@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mbligh@aracnet.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;
as well as URLs for NNTP newsgroup(s).