From: Andi Kleen <andi@firstfloor.org>
To: Richard Yao <shiningarcanine@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does the kernel page the CFS's red-black tree nodes?
Date: Thu, 17 Jun 2010 10:04:55 +0200 [thread overview]
Message-ID: <87r5k6ulso.fsf@basil.nowhere.org> (raw)
In-Reply-To: <AANLkTilOK580U03orIO6jcMvzrHeNsykLSMkdlw0hZLI@mail.gmail.com> (Richard Yao's message of "Tue\, 15 Jun 2010 20\:55\:20 -0400")
Richard Yao <shiningarcanine@gmail.com> writes:
>
> With that said, does the kernel page the CFS's red-black tree nodes to
> swap? If it does, it might be a good idea to reimplement the CFS'
> Red-Black trees in B-Trees, which would minimize slow-downs from
> vm-pressure and also have the additional benefit of minimizing cache
> misses caused by tree traversal.
The kernel does not swap itself, but yes in theory btrees might help to
improve CPU cache locality.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2010-06-17 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTilfw_rXQ4P1jRnrOtun2c9kAq6zNEQHxTF124_x@mail.gmail.com>
2010-06-16 0:55 ` Does the kernel page the CFS's red-black tree nodes? Richard Yao
2010-06-16 11:15 ` Alan Cox
2010-06-17 8:04 ` Andi Kleen [this message]
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=87r5k6ulso.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shiningarcanine@gmail.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