From: "H. Peter Anvin" <hpa@zytor.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Chris Mason <chris.mason@oracle.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC GIT PULL] x86/pat changes for v2.6.34
Date: Mon, 01 Mar 2010 15:24:41 -0800 [thread overview]
Message-ID: <4B8C4CB9.3050901@zytor.com> (raw)
In-Reply-To: <1267468108.16916.937.camel@localhost.localdomain>
On 03/01/2010 10:28 AM, Pallipadi, Venkatesh wrote:
> On Sat, 2010-02-27 at 08:36 -0800, Ingo Molnar wrote:
>> Linus,
>>
>> Please pull the latest x86-pat-for-linus git tree from:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86-pat-for-linus
>>
>> Please have a look at the lib/rbtree.c changes. The rebalancing changes ought
>> to not impact performance - rb_erase() possibly in a small way. Should this
>> perhaps be done via a separate API entry, instead of modifying existing rbtree
>> code?
>>
>> out-of-topic modifications in x86-pat-for-linus:
>> ------------------------------------------------
>> include/linux/rbtree.h # 17d9ddc: rbtree: Add support for augmented
>> lib/rbtree.c # 17d9ddc: rbtree: Add support for augmented
>>
> These patches should go in before "Add support for augmented rbtrees":
>
> "btrfs: use RB_ROOT to intialize rb_trees instead of settingrb_node to
> NULL"
> http://lkml.indiana.edu/hypermail/linux/kernel/1002.2/02946.html
>
> "[patch 0/3] Fixup rb_root initializations to use RB_ROOT"
> http://lkml.indiana.edu/hypermail/linux/kernel/1002.2/03037.html
>
>
>
> And this is an x86 bug fix on top of "Migrate to rbtree only backend for
> pat memtype management"
> http://lkml.indiana.edu/hypermail/linux/kernel/1002.3/00346.html
>
I have added that the latter patch to tip:x86/pat; Ingo should hopefully
run it through his test machine overnight and bump x86-pat-for-linus.
I feel a bit uncomfortable with the btrfs patches just because they're
out of my area, but I'm Cc:ing Chris to let him either take the patches
or tell me to shut up and just do it ;)
-hpa
prev parent reply other threads:[~2010-03-01 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 16:36 [RFC GIT PULL] x86/pat changes for v2.6.34 Ingo Molnar
2010-03-01 18:28 ` Pallipadi, Venkatesh
2010-03-01 23:24 ` H. Peter Anvin [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=4B8C4CB9.3050901@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=venkatesh.pallipadi@intel.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