linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: landley@trommello.org, Rik van Riel <riel@conectiva.com.br>,
	linux-kernel@vger.kernel.org
Subject: Re: Whining about NUMA. :)  [Was whining about 2.5...]
Date: Mon, 08 Oct 2001 11:20:59 -0700	[thread overview]
Message-ID: <1812679136.1002540059@mbligh.des.sequent.com> (raw)
In-Reply-To: <E15qeqz-0001Ne-00@the-village.bc.nu>

>> > speculate on how the 2.4.10 vm works anyway
>> 
>> Can you describe why it's N! ? Are you talking about the worst possible case, 
>> or a two level local / non-local problem?
> 
> Worst possible. I dont think in reality it will be nearly that bad

The worst possible case I can conceive (in the future architectures 
that I know of)  is 4 different levels. I don't think the number of access
speed levels is ever related to the number of processors ?
(users of other NUMA architectures feel free to slap me at this point).

So I *think* the worst possible case is still linear (to number of nodes) 
in terms of how many classzone type things we'd need? And the number 
of classzone type things any given access would have to search through 
for an access is constant? The number of zones searched would be
(worst case) linear to number of nodes?

As we're intending to code this real soon now, this is more than just idle
speculation for my own amusement ;-)

Thanks,

Martin.



  reply	other threads:[~2001-10-08 18:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 12:17 bug? in using generic read/write functions to read/write block devices in 2.4.11-pre2 Vladimir V. Saveliev
2001-10-03 13:16 ` [PATCH] " Alexander Viro
2001-10-03 16:18   ` Linus Torvalds
2001-10-03 21:43     ` Alexander Viro
2001-10-03 21:56       ` Christoph Hellwig
2001-10-03 22:51         ` Alexander Viro
2001-10-03 19:55           ` Whining about 2.5 (was Re: [PATCH] Re: bug? in using generic read/write functions to read/write block devices in 2.4.11-pre2) Rob Landley
2001-10-04  0:38             ` Rik van Riel
2001-10-03 22:27               ` Rob Landley
2001-10-04 20:53                 ` Whining about 2.5 (was Re: [PATCH] Re: bug? in using generic read/write functions to read/write block devices in 2.4.11-pre2O Alan Cox
2001-10-04 23:59                   ` Whining about NUMA. :) [Was whining about 2.5...] Rob Landley
2001-10-05 14:51                     ` Alan Cox
2001-10-08 17:57                       ` Martin J. Bligh
2001-10-08 18:10                         ` Alan Cox
2001-10-08 18:20                           ` Martin J. Bligh [this message]
2001-10-08 18:31                             ` Alan Cox
2001-10-08 18:35                             ` Jesse Barnes
2001-10-08 18:55                               ` Martin J. Bligh
2001-10-08 17:48                                 ` Marcelo Tosatti
2001-10-08 19:20                                   ` Martin J. Bligh
2001-10-08 19:12                                 ` Jesse Barnes
2001-10-08 19:37                                   ` Peter Rival
2001-10-04 23:39                 ` NUMA & classzones (was Whining about 2.5) Martin J. Bligh
2001-10-04 23:55                   ` Rob Landley
2001-10-05 17:29                     ` Martin J. Bligh
2001-10-06  1:44                     ` Jesse Barnes
2001-10-04 21:02             ` Whining about 2.5 (was Re: [PATCH] Re: bug? in using generic read/write functions to read/write block devices in 2.4.11-pre2) Alan Cox
2001-10-03 21:09 ` Buffer cache confusion? Re: [reiserfs-list] bug? in using generic read/write functions to read/write block devices in 2.4.11-pre2 Eric Whiting

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=1812679136.1002540059@mbligh.des.sequent.com \
    --to=martin.bligh@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=landley@trommello.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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).