From: Zachary Amsden <zach@vmware.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Christoph Lameter <clameter@sgi.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
jeremy@goop.org
Subject: Re: [RFC] i386: Remove page sized slabs for pgds and pmds
Date: Wed, 28 Mar 2007 15:42:55 -0800 [thread overview]
Message-ID: <460AFD7F.6050802@vmware.com> (raw)
In-Reply-To: <20070328223327.GG2986@holomorphy.com>
William Lee Irwin III wrote:
>> clone_pgd_range() for consistency? and it seems we lost a
>> paravirt_alloc_pd_clone() in there somewhere.
>>
>
> Yes, another reason why it shouldn't have been posted as-is. It was not
> intended to for anything more than comparative benchmarking on systems
> without graphics running on the bare metal as opposed to Xen/etc. guests.
>
So clone_pgd_range is mostly useless now. Originally, I intended it to
take the part of paravirt_alloc_pd_clone. We should probably merge the
two into just one function, unless someone thinks clone_pgd_range is
actually useful for something.
Zach
next prev parent reply other threads:[~2007-03-28 22:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 20:12 Christoph Lameter
2007-03-28 20:45 ` Andrew Morton
2007-03-28 21:05 ` Christoph Lameter
2007-03-28 21:16 ` William Lee Irwin III
2007-03-28 21:20 ` Christoph Lameter
2007-03-28 22:37 ` William Lee Irwin III
2007-03-28 23:44 ` Christoph Lameter
2007-03-29 0:53 ` William Lee Irwin III
2007-03-29 1:09 ` Christoph Lameter
2007-03-29 1:17 ` Benjamin LaHaise
2007-03-28 20:50 ` William Lee Irwin III
2007-03-28 21:00 ` Christoph Lameter
2007-03-28 21:24 ` William Lee Irwin III
2007-03-28 21:38 ` Christoph Lameter
2007-03-28 22:01 ` William Lee Irwin III
2007-03-28 22:22 ` Christoph Lameter
2007-03-29 0:28 ` Alan Cox
2007-03-29 0:59 ` William Lee Irwin III
2007-03-28 22:26 ` Chris Wright
2007-03-28 22:33 ` William Lee Irwin III
2007-03-28 22:45 ` Chris Wright
2007-03-28 23:42 ` Zachary Amsden [this message]
2007-03-28 22:47 ` Chris Wright
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=460AFD7F.6050802@vmware.com \
--to=zach@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=clameter@sgi.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®