From: Pavel Machek <pavel@suse.cz>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Jamie Lokier <lk@tantalophile.demon.co.uk>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: /proc/<n>/maps getting _VERY_ long
Date: Sat, 11 Aug 2001 01:04:11 +0000 [thread overview]
Message-ID: <20010811010411.A55@toy.ucw.cz> (raw)
In-Reply-To: <20010806194120.A5803@thefinal.cern.ch> <Pine.LNX.4.33.0108101445350.7596-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0108101445350.7596-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Fri, Aug 10, 2001 at 02:55:11PM -0700
Hi!
> > There are garbage collectors that use mprotect() and SEGV trapping per
> > page. It would be nice if there was a way to change the protections per
> > page without requiring a VMA for each one.
>
> This is actually how Linux used to work a long long time ago - all
> protection information was in the page tables, and you could do per-page
> things without having to worry about piddling details like vma's.
>
> It does work, but it had major downsides. Trivial things like re-creating
> the permission after throwing a page out or swapping it out.
For some uses, spurious SEGV after swap-in might be okay ;-). Garbage
collector might be that example. Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2001-08-14 11:49 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
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 [this message]
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=20010811010411.A55@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).