From: Tejun Heo <tj@kernel.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Reverting NUMA-affine page table allocation
Date: Wed, 2 Mar 2011 18:07:02 +0100 [thread overview]
Message-ID: <20110302170702.GS3319@htj.dyndns.org> (raw)
In-Reply-To: <AANLkTi=SYRK+iKT-Zwuyv=e6dLqmoL4cUts2Xoyq-M=1@mail.gmail.com>
Hello,
On Wed, Mar 02, 2011 at 08:47:54AM -0800, Yinghai Lu wrote:
> > > Yeah, it's a pretty interesting piece of code in need of some cleanup.
> No, i mean second one is not causing any problem.
>
> that only take end is intentionally. that will make sure we can get
> space for page table even in extreme case.
Hmmm... it seems like it only took @end because it always allocated
the whole page table in one go. Always from the bottom to top. Am I
missing something?
> > > If you're interested in doing the above, please go ahead and let me
> > > know.
>
> No. please don't revert it.
>
> Ingo, please get patches that will align to 1G ... from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-2.6-yinghai.git memblock
If you were gonna do that, you could have just said that you objected
to the reverting. The message was Request for Comments - soliciting
responses.
As I wrote multiple times, I think the code as implemented is a bit
heavy handed for the problem. And a bigger problem for me is that it
kind of just piles on the existing messiness and worsens it. I really
hope we wouldn't be doing that anymore.
I tried to clean up the page table allocation code but the necessary
changes felt a bit too large at this stage, so IMO that's best left to
the next cycle.
To me, it seems complicated for not good enough reasons. I'll defer
the decision to x86 maintainers. Ingo, hpa, Thomas, what do you guys
think?
Thanks.
--
tejun
next prev parent reply other threads:[~2011-03-02 17:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 14:37 [RFC] Reverting NUMA-affine page table allocation Tejun Heo
2011-03-01 8:30 ` Tejun Heo
2011-03-01 22:41 ` Yinghai Lu
2011-03-02 16:19 ` Tejun Heo
2011-03-02 16:47 ` Yinghai Lu
2011-03-02 17:07 ` Tejun Heo [this message]
2011-03-02 18:08 ` Ingo Molnar
2011-03-02 18:12 ` H. Peter Anvin
2011-03-02 18:19 ` Ingo Molnar
2011-03-02 18:25 ` Tejun Heo
2011-03-02 18:31 ` Ingo Molnar
2011-03-02 18:32 ` Ingo Molnar
2011-03-02 18:22 ` Tejun Heo
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=20110302170702.GS3319@htj.dyndns.org \
--to=tj@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=yinghai@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