From: "David S. Miller" <davem@redhat.com>
To: davidel@xmailserver.org
Cc: ralf@conectiva.com.br, torvalds@transmeta.com,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
andrea@suse.de, manfred@colorfullife.com, riel@conectiva.com.br
Subject: Re: Purpose of the mm/slab.c changes
Date: Sat, 22 Sep 2001 14:36:24 -0700 (PDT) [thread overview]
Message-ID: <20010922.143624.59468806.davem@redhat.com> (raw)
In-Reply-To: <XFMail.20010922140302.davidel@xmailserver.org>
In-Reply-To: <20010922142847.A20641@dea.linux-mips.net> <XFMail.20010922140302.davidel@xmailserver.org>
From: Davide Libenzi <davidel@xmailserver.org>
Date: Sat, 22 Sep 2001 14:03:02 -0700 (PDT)
Besides this, i don't get how a LIFO could help you.
Actually, there is a school of thought which says that if you make the
time between the free and re-alloc of a piece of memory as long as
possible you increase the likelyhood that any dirty cache lines of
that memory can be sent back to memory "quietly" during natural L2
cache line replacement.
I don't necessarily subscribe to these ideas, but I do see the
potential benefits. For one thing, it does have the potential to lead
to more repeatable timings, at least in theory.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-09-22 21:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-09 11:05 Purpose of the mm/slab.c changes Manfred Spraul
2001-09-09 14:26 ` Andrea Arcangeli
2001-09-09 15:18 ` Manfred Spraul
2001-09-09 15:33 ` Andrea Arcangeli
2001-09-11 18:41 ` Manfred Spraul
2001-09-11 19:36 ` Andrea Arcangeli
2001-09-11 20:43 ` Manfred Spraul
2001-09-12 14:18 ` Andrea Arcangeli
2001-09-09 16:12 ` Alan Cox
2001-09-09 16:25 ` Linus Torvalds
2001-09-09 16:47 ` Alan Cox
2001-09-09 16:55 ` Manfred Spraul
2001-09-09 17:01 ` Linus Torvalds
2001-09-09 17:22 ` Manfred Spraul
2001-09-09 17:27 ` arjan
2001-09-09 17:35 ` Andrea Arcangeli
2001-09-09 17:30 ` Andrea Arcangeli
2001-09-09 17:59 ` Fwd: 2.4.10-pre6 ramdisk driver broken? won't compile Stephan Gutschke
2001-09-09 20:26 ` Purpose of the mm/slab.c changes Rik van Riel
2001-09-15 0:29 ` Albert D. Cahalan
2001-09-09 20:23 ` Rik van Riel
2001-09-09 20:44 ` Davide Libenzi
2001-09-09 20:45 ` Rik van Riel
2001-09-09 20:58 ` Davide Libenzi
2001-09-22 12:28 ` Ralf Baechle
2001-09-22 21:03 ` Davide Libenzi
2001-09-22 21:36 ` David S. Miller [this message]
2001-09-10 2:28 ` Daniel Phillips
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=20010922.143624.59468806.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=ralf@conectiva.com.br \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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