mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: ebiederm@xmission.com (Eric W. Biederman),
	Rik van Riel <riel@conectiva.com.br>,
	Adam Kropelin <akropel1@rochester.rr.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.18pre3-ac1
Date: Sun, 20 Jan 2002 22:30:26 -0700	[thread overview]
Message-ID: <200201210530.g0L5UQu20723@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <E16SVPU-0001dp-00@starship.berlin>
In-Reply-To: <Pine.LNX.4.33L.0201140409260.32617-100000@imladris.surriel.com> <m1y9j1pf6r.fsf@frodo.biederman.org> <E16SVPU-0001dp-00@starship.berlin>

Daniel Phillips writes:
> The way I see it, the purpose of lazy page table instantiation is to
> overcome objections to the reverse pte mapping vm technique that
> have been expressed in the past, namely the slowdown in dup_mmap
> inside fork.  I.e., if rmap slows down fork then Linus and Davem are
> going to veto it, as they've done in the past, because they feel
> that the as-yet-unproven advantages of physically-based vm scanning
> doesn't outweigh the easily measurable fork overhead.  Personally, I
> think that's debatable, but by eliminating the overhead we eliminate
> the objection, and as far as I know, it's the only serious
> objection.

Will lazy page table instantiation speed up fork(2) without rmap?
If so, then you've got a problem, because rmap will still be slower
than non-rmap. Linus will happily grab any speedup and make that the
new baseline against which new schemes are compared :-)

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2002-01-21  5:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 21:44 Alan Cox
2002-01-13 19:23 ` Thiago Rondon
2002-01-13 22:52 ` Ville Herva
2002-01-13 22:57   ` Alan Cox
2002-01-14  0:15 ` Adam Kropelin
2002-01-14  0:47   ` Alan Cox
2002-01-14  2:13     ` Benjamin LaHaise
2002-01-14  2:54   ` Rik van Riel
2002-01-14  5:47     ` Eric W. Biederman
2002-01-14  6:17       ` Rik van Riel
2002-01-14  7:25         ` Eric W. Biederman
2002-01-21  3:46           ` Daniel Phillips
2002-01-21  5:30           ` Richard Gooch [this message]
2002-01-21  5:34             ` Rik van Riel
2002-01-21  7:01               ` Eric W. Biederman
2002-01-21 12:02                 ` Rik van Riel
2002-01-21 14:02                 ` Daniel Phillips
2002-01-21 13:22             ` Daniel Phillips
2002-01-14  9:28         ` David S. Miller
2002-01-14 12:05           ` Rik van Riel

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=200201210530.g0L5UQu20723@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=akropel1@rochester.rr.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    --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

all inboxes | Powered by JetHome®