From: Andrew Morton <akpm@linux-foundation.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Nish Aravamudan <nish.aravamudan@gmail.com>,
Ken Chen <kenchen@google.com>, Adam Litke <agl@us.ibm.com>,
Arjan van de Ven <arjan@infradead.org>,
William Lee Irwin III <wli@holomorphy.com>,
Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] rfc: introduce /dev/hugetlb
Date: Fri, 23 Mar 2007 23:41:56 -0800 [thread overview]
Message-ID: <20070323234156.72b955e9.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070324065752.GA13810@uranus.ravnborg.org>
On Sat, 24 Mar 2007 07:57:52 +0100 Sam Ravnborg <sam@ravnborg.org> wrote:
> >
> > But for non-programming reasons, we're just not there yet: people want to
> > program direct to the kernel interfaces simply because of the
> > distribution/coordination problems with libraries. It would be nice to fix
> > that problem.
>
> What is then needed to get a small subset of user-space in the kernel-development cycle?
Someone to lead the work, mainly. It would be a large effort, a lot of
time and email traffic.
> Maybe a topic worth to take up at LKS...
Well, perhaps. But unless someone with suitable experience has enough time
and energy to spare to make it happen, it won't be happening.
next prev parent reply other threads:[~2007-03-24 7:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 8:44 Ken Chen
2007-03-23 15:03 ` William Lee Irwin III
2007-03-23 21:56 ` Ken Chen
2007-03-23 15:03 ` Mel Gorman
2007-03-23 15:09 ` William Lee Irwin III
2007-03-23 15:15 ` Mel Gorman
2007-03-23 15:30 ` William Lee Irwin III
2007-03-23 22:04 ` Ken Chen
2007-03-23 21:08 ` Benjamin Herrenschmidt
2007-03-24 4:58 ` Andrew Morton
2007-03-24 5:32 ` Nish Aravamudan
2007-03-24 6:12 ` Andrew Morton
2007-03-24 6:57 ` Sam Ravnborg
2007-03-24 7:41 ` Andrew Morton [this message]
2007-03-24 7:11 ` Ken Chen
2007-03-24 7:39 ` Andrew Morton
2007-03-25 10:22 ` Arjan van de Ven
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=20070323234156.72b955e9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agl@us.ibm.com \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nish.aravamudan@gmail.com \
--cc=sam@ravnborg.org \
--cc=wli@holomorphy.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
Powered by JetHome