public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: "David S. Miller" <davem@redhat.com>,
	David Luyer <david_luyer@pacific.net.au>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: /proc/<n>/maps growing...
Date: Tue, 7 Aug 2001 00:26:50 +1200	[thread overview]
Message-ID: <20010807002650.B23937@weta.f00f.org> (raw)
In-Reply-To: <997080081.3938.28.camel@typhaon> <20010806105904.A28792@athlon.random> <15214.24938.681121.837470@pizda.ninka.net> <20010806125705.I15925@athlon.random>
In-Reply-To: <20010806125705.I15925@athlon.random>

On Mon, Aug 06, 2001 at 12:57:05PM +0200, Andrea Arcangeli wrote:

    The point here is not if it's simple or difficult. The point is what can
    be done or not and what is faster or slower. All I'm saying is that I
    don't see why it's not possible to implement the merge_segments with
    only an O(1) additional cost of a few cycles per mmap syscall, which
    will render the feature an obvious improvement (instead of being a
    dubious improvement like in 2.2 that is walking the tree two times).

mmap does merge in many common cases.



  --cw

  reply	other threads:[~2001-08-06 12:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-06  6:41 /proc/<n>/maps growing David Luyer
2001-08-06  7:43 ` Chris Wedgwood
2001-08-06  8:59 ` Andrea Arcangeli
2001-08-06  9:20   ` David S. Miller
2001-08-06  9:46     ` Chris Wedgwood
2001-08-06 10:57     ` Andrea Arcangeli
2001-08-06 12:26       ` Chris Wedgwood [this message]
2001-08-06 12:36         ` Andrea Arcangeli
2001-08-06 12:45           ` Chris Wedgwood
2001-08-06 12:50             ` Andrea Arcangeli
2001-08-06 13:06               ` David S. Miller
2001-08-06 13:29                 ` Andrea Arcangeli
2001-08-06 17:27                   ` Linus Torvalds
2001-09-03 15:44                     ` mmap-rb-7 [was Re: /proc/<n>/maps growing...] Andrea Arcangeli
2001-08-06 17:20           ` /proc/<n>/maps growing Linus Torvalds
2001-08-07  2:24             ` David Luyer
2001-08-06 17:46           ` Anton Altaparmakov
2001-08-06 16:12     ` Rik van Riel
2001-08-06 17:46       ` Linus Torvalds
2001-08-06 10:30   ` Jakub Jelinek
2001-08-06 10:49     ` Andrea Arcangeli
2001-08-06 11:01       ` Jakub Jelinek
2001-08-06 11:25         ` Andrea Arcangeli
2001-08-06 17:17         ` Linus Torvalds
2001-08-06 17:26           ` Alan Cox
2001-08-06 22:55             ` Chris Wedgwood
2001-08-06 11:16       ` Jakub Jelinek
2001-08-06 17:18       ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2001-08-07  3:46 Rick Hohensee

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=20010807002650.B23937@weta.f00f.org \
    --to=cw@f00f.org \
    --cc=andrea@suse.de \
    --cc=davem@redhat.com \
    --cc=david_luyer@pacific.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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