From: Chris Wedgwood <cw@f00f.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Rik van Riel <riel@conectiva.com.br>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: /proc/<n>/maps getting _VERY_ long
Date: Mon, 6 Aug 2001 01:18:59 +1200 [thread overview]
Message-ID: <20010806011859.A21830@weta.f00f.org> (raw)
In-Reply-To: <20010805171202.A20716@weta.f00f.org> <E15TNbk-0007pu-00@the-village.bc.nu>
In-Reply-To: <E15TNbk-0007pu-00@the-village.bc.nu>
On Sun, Aug 05, 2001 at 02:06:16PM +0100, Alan Cox wrote:
Linus took itout because it was quite complex and nobody seemed to
have cases that triggered it or made it useful
Hmm... well it seems the are cases which trigger this, mozilla and
vmware being quite common.
Is a less heavy-handed approach than the original code possible?
Something like when inserting into a processes vma, if there are more
than <n> entries, we lock/scan/coalesce/unlock --- or would this
locking be too gross?
--cw
next prev parent reply other threads:[~2001-08-05 13:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-04 15:43 /proc/<n>/maps getting _VERY_ long Chris Wedgwood
2001-08-05 2:17 ` Rik van Riel
2001-08-05 5:12 ` Chris Wedgwood
2001-08-05 13:06 ` Alan Cox
2001-08-05 13:18 ` Chris Wedgwood [this message]
2001-08-05 23:07 ` Jakob Østergaard
2001-08-05 23:41 ` Linus Torvalds
2001-08-06 0:41 ` Michael H. Warfield
2001-08-06 1:01 ` Linus Torvalds
2001-08-06 1:17 ` H. Peter Anvin
2001-08-06 4:26 ` Linus Torvalds
2001-08-06 6:30 ` H. Peter Anvin
2001-08-06 18:41 ` Jamie Lokier
2001-08-10 21:55 ` Linus Torvalds
2001-08-10 22:00 ` H. Peter Anvin
2001-08-10 23:03 ` Nicolas Pitre
2001-08-10 23:26 ` Linus Torvalds
2001-08-10 23:55 ` Rik van Riel
2001-08-11 1:04 ` Pavel Machek
2001-08-06 11:52 ` Alan Cox
2001-08-06 12:23 ` Chris Wedgwood
2001-08-06 13:17 ` Alan Cox
2001-08-06 13:55 ` Chris Wedgwood
2001-08-06 9:43 ` [LONGish] Brief analysis of VMAs (was: /proc/<n>/maps getting _VERY_ long) Chris Wedgwood
2001-08-05 6:44 /proc/<n>/maps getting _VERY_ long David Luyer
2001-08-05 7:21 ` Anders Eriksson
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=20010806011859.A21830@weta.f00f.org \
--to=cw@f00f.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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).