From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Bindings for ‘sendfile’
Date: Wed, 17 Apr 2013 17:18:15 +0200 [thread overview]
Message-ID: <8738upyymg.fsf@zigzag.favinet> (raw)
In-Reply-To: <87fvyp9v53.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 17 Apr 2013 14:52:40 +0200")
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
() ludo@gnu.org (Ludovic Courtès)
() Wed, 17 Apr 2013 14:52:40 +0200
concrete cases of recurring short writes?
The original application was "ttn-do serve-debiso", which configures
"ttn-do sizzweb" to serve debian ISOs (or rather, the various component
.deb files and metadata that apt-get requests from the loopback-mounted
ISO) over the home network.
Specifically, proc ‘prep-file-transfer’ in module ‘(ttn-do sizzweb)’
calls ‘sendfile’ in a loop. Admittedly, that code could be replaced by
‘sendfile/never-fewer’, as the retval is not used in a particularly
intelligent way, but anyway, the point is, at time of writing and early
testing *sans looping*, apt-get on the other computer would stall and
eventually die, complaining. That's when i learned to read and think
about sendfile(2) more carefully than i had before.
It would be nice to point to a ChangeLog entry that embodies this "ah
ha!" moment, but as it turned out, the testing was done before commit.
Oh well, life goes on...
--
Thien-Thi Nguyen
GPG key: 4C807502
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-04-17 15:18 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
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 [this message]
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=8738upyymg.fsf@zigzag.favinet \
--to=ttn@gnuvola.org \
--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).