linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: New syscall: leftpad()
Date: Thu, 31 Mar 2016 16:36:24 -0700	[thread overview]
Message-ID: <56FDB478.4020609@infradead.org> (raw)
In-Reply-To: <1459463613-32473-1-git-send-email-richard-/L3Ra7n9ekc@public.gmane.org>

Please be more careful in your description...

On 03/31/16 15:33, Richard Weinberger wrote:
> Recent happenings in the node.js community showed how fragile software is when
> it comes to dependencies of fundamental algorithms like leftpad[1].
> A node.js package which provided ledpad vanished and broke a lot of software.

                                   leftpad

> This raised our attention and we came to the conclusion that it is the kernel's
> job to provide such functionality such that node.js based applications can in future
> rely in Linux's "don't break userspace" rule.
> We hope that glibc and Andoid's bionic will soon offer wrapper functions for this

                         Android's

> new leftpad system call.
> We put leftpad into the kernel not only because of Linux's stable ABI,
> also for performance reasons.
> As everyone knows, within the kernel everything is faster and better.
> Leftpad has millions of users, so it has to be as fast as possible.
> This new system call will also help making services like left-pad.io[2]
> faster and more reliable. If the leftpad() system call gets adopted by a wider user base
> it might also make sense to add a generic npm() system call which acts like ioctl()
> where kernel modules can register new functions that are often used by node.js.
> Such functions might be, is_array(), is_int(), etc.


-- 
~Randy

  parent reply	other threads:[~2016-03-31 23:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31 22:33 New syscall: leftpad() Richard Weinberger
2016-03-31 22:33 ` [PATCH] Implement leftpad syscall Richard Weinberger
     [not found]   ` <1459463613-32473-2-git-send-email-richard-/L3Ra7n9ekc@public.gmane.org>
2016-03-31 22:46     ` Michael Kerrisk (man-pages)
2016-03-31 23:09     ` Greg KH
2016-04-01  3:22     ` kbuild test robot
2016-04-01  6:56     ` Richard Cochran
2016-04-01  1:33   ` Frederic Weisbecker
2016-04-01  7:14   ` Scotty Bauer
2016-03-31 22:33 ` [PATCH] leftpad.2: Document new syscall Richard Weinberger
     [not found]   ` <1459463613-32473-3-git-send-email-richard-/L3Ra7n9ekc@public.gmane.org>
2016-04-08 18:10     ` Heinrich Schuchardt
2016-04-09 14:12       ` Richard Weinberger
     [not found] ` <1459463613-32473-1-git-send-email-richard-/L3Ra7n9ekc@public.gmane.org>
2016-03-31 23:36   ` Randy Dunlap [this message]
     [not found]     ` <56FDB478.4020609-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-04-01  8:06       ` New syscall: leftpad() Richard Weinberger

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=56FDB478.4020609@infradead.org \
    --to=rdunlap-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=richard-/L3Ra7n9ekc@public.gmane.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;
as well as URLs for NNTP newsgroup(s).