linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Christopher Yeoh <cyeoh@au1.ibm.com>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-mm@kvack.org, Brice Goglin <Brice.Goglin@inria.fr>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [RFC][PATCH] Cross Memory Attach v2 (resend)
Date: Fri, 26 Nov 2010 00:09:03 -0800	[thread overview]
Message-ID: <20101126000903.df846d3e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20101126080624.GA26764@elte.hu>

On Fri, 26 Nov 2010 09:06:24 +0100 Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > On Mon, 22 Nov 2010 12:28:47 +1030
> > Christopher Yeoh <cyeoh@au1.ibm.com> wrote:
> > 
> > > Resending just in case the previous mail was missed rather than ignored :-)
> > > I'd appreciate any comments....
> > 
> > Fear, uncertainty, doubt and resistance!
> > 
> > We have a bit of a track record of adding cool-looking syscalls and
> > then regretting it a few years later.  Few people use them, and maybe
> > they weren't so cool after all, and we have to maintain them for ever. 
> 
> They are often cut off at the libc level and never get into apps.
> 
> If we had tools/libc/ (mapped by the kernel automagically via the vDSO), where 
> people could add new syscall usage to actual, existing, real-life libc functions, 
> where the improvements could thus propagate into thousands of apps immediately, 
> without requiring any rebuild of apps or even any touching of the user-space 
> installation, we'd probably have _much_ more lively development in this area.
> 
> Right now it's slow and painful, and few new syscalls can break through the brick 
> wall of implementation latency, app adoption disinterest due to backwards 
> compatibility limitations and the resulting inevitable lack of testing and lack of 
> tangible utility.

Can't people use libc's syscall(2)?

--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-11-26  8:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22  1:58 Christopher Yeoh
2010-11-22 21:05 ` Andrew Morton
2010-11-23  9:25   ` Christopher Yeoh
2010-11-23 10:05     ` Brice Goglin
2010-12-03  5:37       ` Robin Holt
2010-11-26  8:06   ` Ingo Molnar
2010-11-26  8:09     ` Andrew Morton [this message]
2010-11-26  8:41       ` Ingo Molnar

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=20101126000903.df846d3e.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Brice.Goglin@inria.fr \
    --cc=cyeoh@au1.ibm.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox