From: Noah Lavine <noah.b.lavine@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Bindings for ‘sendfile’
Date: Thu, 21 Mar 2013 11:39:53 -0400 [thread overview]
Message-ID: <CA+U71=PyRec7SB+pmUUAX-WWiXq2GiwzUHj+j_oq3xOHObf1iw@mail.gmail.com> (raw)
In-Reply-To: <8738vp3yhe.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
Hello,
Yes, you're completely right - making it work on all platforms is much
better than what I had proposed. I'm glad you're doing this.
Thanks,
Noah
On Thu, Mar 21, 2013 at 5:15 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Hi Noah,
>
> Noah Lavine <noah.b.lavine@gmail.com> skribis:
>
> > I've thought for a while that if I had time (which I know I won't) I
> would
> > make a module called (linux) with bindings for non-POSIX Linux kernel
> > features. What do you think of this idea? If so, what do you think of
> > putting sendfile there and expanding it with other functions as we need
> > them?
>
> I’ve thought about it, but ended up with making sendfile work whether or
> not the syscall is available (just like glibc does, after all).
>
> So for this particular case, I’d rather keep it in the global name
> space. There’s also the untold argument that even if sendfile(2) is
> unavailable, the loop written in C is going to be faster than the
> equivalent bytecode.
>
> FWIW, I plan to integrate the Linux bindings I wrote for “boot-to-Guile”
> eventually:
>
>
> http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/patches/guile-linux-syscalls.patch
>
> These are not defined in POSIX, but apart from the Linux module
> syscalls, they (that is, mount(2) and the networking ioctls) happen to
> be supported by glibc on all 3 kernels, and also by other libcs. Thus,
> I’d rather keep them in the global name space as well.
>
> WDYT?
>
> Thanks,
> Ludo’.
>
[-- Attachment #2: Type: text/html, Size: 2146 bytes --]
next prev parent reply other threads:[~2013-03-21 15:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 22:21 [PATCH] Bindings for ‘sendfile’ Ludovic Courtès
2013-03-21 0:17 ` Noah Lavine
2013-03-21 9:15 ` Ludovic Courtès
2013-03-21 10:04 ` Andrew Gaylard
2013-03-21 15:39 ` Noah Lavine [this message]
2013-03-21 3:45 ` Nala Ginrut
2013-03-21 4:50 ` Mark H Weaver
2013-03-21 5:24 ` Mark H Weaver
2013-03-21 9:40 ` Ludovic Courtès
2013-03-21 9:49 ` Andy Wingo
2013-03-21 10:10 ` Ludovic Courtès
2013-03-22 19:22 ` Mark H Weaver
2013-03-22 21:27 ` Ludovic Courtès
2013-03-24 5:04 ` Mark H Weaver
2013-03-25 12:55 ` Ludovic Courtès
2013-04-07 19:53 ` Ludovic Courtès
2013-04-09 8:33 ` Thien-Thi Nguyen
2013-04-09 15:02 ` Ludovic Courtès
2013-04-09 20:34 ` Thien-Thi Nguyen
2013-04-10 11:26 ` Mark H Weaver
2013-04-14 10:48 ` Thien-Thi Nguyen
2013-04-16 16:31 ` Ludovic Courtès
2013-04-16 20:14 ` Thien-Thi Nguyen
2013-04-17 12:52 ` Ludovic Courtès
2013-04-17 15:18 ` Thien-Thi Nguyen
2013-04-17 16:27 ` Ludovic Courtès
2013-04-18 6:58 ` Thien-Thi Nguyen
2013-04-10 20:56 ` Ludovic Courtès
2013-04-14 10:52 ` Thien-Thi Nguyen
2013-04-07 21:51 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+U71=PyRec7SB+pmUUAX-WWiXq2GiwzUHj+j_oq3xOHObf1iw@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).