linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Tejun Heo <tj@kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	cpw@sgi.com
Subject: Re: #tj-percpu has been rebased
Date: Tue, 17 Feb 2009 22:40:20 -0800	[thread overview]
Message-ID: <499BAD54.3050108@zytor.com> (raw)
In-Reply-To: <200902181455.11572.rusty@rustcorp.com.au>

Rusty Russell wrote:
>>>
>> num_possible_cpus() can be very large though, so in many cases the
>> likelihood of finding that many pages approach zero.  Furthermore,
>> num_possible_cpus() may be quite a bit larger than the actual number of
>> CPUs in the system.
> 
> Sure, so we end up at vmalloc.  No worse, but simpler and much better if we
> *can* do it.
> 

If the likelihood is near zero, then you're wasting opportunities to do
it better.  If we have compact per-cpu virtual areas then we can use
large pages if we know we'll have large percpu areas.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2009-02-18  6:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 17:05 #tj-percpu has been rebased Tejun Heo
2009-01-31  5:46 ` Tejun Heo
2009-01-31 13:28   ` Ingo Molnar
2009-02-02  9:04   ` Rusty Russell
2009-02-04  3:18     ` Tejun Heo
2009-02-12  3:37       ` Tejun Heo
2009-02-12  3:44         ` Tejun Heo
2009-02-13 20:58           ` Rusty Russell
2009-02-13 21:17             ` Jeremy Fitzhardinge
2009-02-13 22:59             ` H. Peter Anvin
2009-02-14  0:45             ` Tejun Heo
2009-02-14  1:53               ` H. Peter Anvin
2009-02-14  2:10                 ` Tejun Heo
2009-02-16  7:23               ` Rusty Russell
2009-02-16 17:28                 ` H. Peter Anvin
2009-02-16 23:22                   ` Rusty Russell
2009-02-16 23:28                     ` H. Peter Anvin
2009-02-18  4:25                       ` Rusty Russell
2009-02-18  6:40                         ` H. Peter Anvin [this message]
2009-02-18  7:11                           ` Rusty Russell

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=499BAD54.3050108@zytor.com \
    --to=hpa@zytor.com \
    --cc=cpw@sgi.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).