From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Huge TLB pages always physically continious?
Date: Sat, 02 Nov 2002 03:29:40 -0500 [thread overview]
Message-ID: <3DC38CF4.1060301@pobox.com> (raw)
In-Reply-To: 3DC30CD6.D92D0F9F@digeo.com
Now that hugetlbfs is merged, can we remove the hugetlb syscalls?
Pretty please? ;-)
What I've heard in the background is that all the Big Users(tm) of
hugetlbs greatly prefer the existing syscalls (a.k.a. hugetlbfs) to
adding support to new ones in the various userland portability layers in
use...
Jeff
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Huge TLB pages always physically continious?
Date: Sat, 02 Nov 2002 03:29:40 -0500 [thread overview]
Message-ID: <3DC38CF4.1060301@pobox.com> (raw)
In-Reply-To: 3DC30CD6.D92D0F9F@digeo.com
Now that hugetlbfs is merged, can we remove the hugetlb syscalls?
Pretty please? ;-)
What I've heard in the background is that all the Big Users(tm) of
hugetlbs greatly prefer the existing syscalls (a.k.a. hugetlbfs) to
adding support to new ones in the various userland portability layers in
use...
Jeff
--
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/
next prev parent reply other threads:[~2002-11-02 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 22:56 Huge TLB pages always physically continious? Ingo Oeser
2002-11-01 23:23 ` Andrew Morton
2002-11-01 23:23 ` Andrew Morton
2002-11-02 8:29 ` Jeff Garzik [this message]
2002-11-02 8:29 ` Jeff Garzik
2002-11-04 13:49 ` get_user_pages rewrite (was: Huge TLB pages always physically continious?) Ingo Oeser
2002-11-04 13:49 ` Ingo Oeser
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=3DC38CF4.1060301@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@digeo.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.