From: Linus Torvalds <torvalds@transmeta.com>
To: Gerrit Huizenga <gh@us.ibm.com>
Cc: Andrew Morton <akpm@zip.com.au>,
"Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
Hubertus Franke <frankeh@watson.ibm.com>,
wli@holomorpy.com, swj@cse.unsw.edu.au,
linux-mm mailing list <linux-mm@kvack.org>
Subject: Re: large page patch (fwd) (fwd)
Date: Fri, 2 Aug 2002 21:39:28 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0208022136380.2733-100000@home.transmeta.com> (raw)
In-Reply-To: <E17aqUv-000344-00@w-gerrit2>
On Fri, 2 Aug 2002, Gerrit Huizenga wrote:
> In message <Pine.LNX.4.44.0208021757490.2210-100000@home.transmeta.com>, > : Li
> nus Torvalds writes:
> >
> >
> > On Fri, 2 Aug 2002, Andrew Morton wrote:
> > >
> > > Remind me again what's wrong with wrapping the Intel syscalls
> > > inside malloc() and then maybe grafting a little hook into the shm code?
> >
> > Indeed.
>
> Do you really want all calls to malloc to allocate non-pageable
> memory? And I doubt that this memory will be pageable in time for
> 2.5.
No, I'm saying that you can do the SHM_LARGEPAGE bit testing in user space
if you want to.
And obviously it will only succeed for root or similar user anyway.
But hey, the proof is in the pudding. If you guys can come up with a
better scheme that does not pollute the VM paths and has better semantics,
I don't think anybody will complain.
Linus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2002-08-03 4:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0208021252090.2466-100000@penguin.transmeta.com>
2002-08-02 23:54 ` Martin J. Bligh
2002-08-03 0:35 ` Andrew Morton
2002-08-03 1:26 ` Linus Torvalds
2002-08-03 4:26 ` Gerrit Huizenga
2002-08-03 4:39 ` Linus Torvalds [this message]
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=Pine.LNX.4.44.0208022136380.2733-100000@home.transmeta.com \
--to=torvalds@transmeta.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=frankeh@watson.ibm.com \
--cc=gh@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=swj@cse.unsw.edu.au \
--cc=wli@holomorpy.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