From: Antonio Vargas <wind@cocodriloo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Antonio Vargas <wind@cocodriloo.com>,
Timothy Miller <tmiller10@cfl.rr.com>,
linux-kernel@vger.kernel.org, nicoya@apia.dhs.org
Subject: Re: Quick question about hyper-threading (also some NUMA stuff)
Date: Mon, 14 Apr 2003 19:14:19 +0200 [thread overview]
Message-ID: <20030414171419.GG14552@wind.cocodriloo.com> (raw)
In-Reply-To: <15700000.1050338226@[10.10.2.4]>
On Mon, Apr 14, 2003 at 09:37:07AM -0700, Martin J. Bligh wrote:
> >> OK, unless I misunderstand you, I think that happens naturally for that
> >> kind of thing - when we do the COW split, we'll get a node-local page
> >> by default (unless the local node is out of memory).
> >
> > Yes, it happens naturaly, but it's done when we try to write to it.
> > What I meant was, at fork time, it we are forking to a different node,
> > instead of COW-marking, do the COW-mark and the immediately do a sort-of
> > for_each_page(touch_as_if_written(page)), so that nodes would not have to
> > reference the memory from others.
>
> Ah, you probably don't want to do that ... it's very expensive. Moreover,
> if you exec 2ns later, all the effort will be wasted ... and it's very hard
> to deterministically predict whether you'll exec or not (stupid UNIX
> semantics). Doing it lazily is probably best, and as to "nodes would not
> have to reference the memory from others" - you're still doing that, you're
> just batching it on the front end.
True... What about a vma-level COW-ahead just like we have a file-level
read-ahead, then? I mean batching the COW at unCOW-because-of-write time.
btw, COW-ahead sound really silly :)
> > I don't know if it's really usefull, and anyways I could not try to code it
> > unless there is a sort of NUMA simulator for "normal" machines.
>
> There isn't, but writing one would be very useful (and fairly simple) if
> you have a 2x machine or something that you could use. I've thought about
> writing this several times ... just haven't got round to it.
>
> M.
Not possible for me since I've got no SMP. But posting a quick note about
your proposed "fake-NUMA-on-SMP.patch" would be good only if to have an
offsite (offbrain also? ;) backup of your ideas :)
next prev parent reply other threads:[~2003-04-14 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 13:31 Quick question about hyper-threading (also some NUMA stuff) Timothy Miller
2003-04-14 14:55 ` Martin J. Bligh
2003-04-14 15:29 ` Antonio Vargas
2003-04-14 15:39 ` Martin J. Bligh
2003-04-14 15:57 ` Antonio Vargas
2003-04-14 16:24 ` Martin J. Bligh
2003-04-14 16:43 ` Antonio Vargas
2003-04-14 16:37 ` Martin J. Bligh
2003-04-14 17:14 ` Antonio Vargas [this message]
2003-04-14 17:22 ` Martin J. Bligh
2003-04-14 18:32 ` cow-ahead N pages for fault clustering Antonio Vargas
2003-04-14 18:47 ` Antonio Vargas
2003-04-15 5:49 ` Martin J. Bligh
2003-04-18 17:35 ` Antonio Vargas
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=20030414171419.GG14552@wind.cocodriloo.com \
--to=wind@cocodriloo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=nicoya@apia.dhs.org \
--cc=tmiller10@cfl.rr.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