mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Moritz Wilhelmy <ml+musl@wzff.de>
To: musl@lists.openwall.com
Subject: Re: Anti-bloat side project
Date: Tue, 16 Aug 2011 15:03:50 +0200	[thread overview]
Message-ID: <20110816130350.GF26140@barfooze.de> (raw)
In-Reply-To: <20110629200358.GN5036@port70.net>

Hello,

While debugging mlmmj, my mailing list manager of choice, I noted that
it calls read(2) really, really often, in order to read a single byte
out of a fd, and then read the next byte, like this:

open("/var/spool/mlmmj/foo/control/listaddress", O_RDONLY) = 4
read(4, "f", 1)                         = 1
read(4, "o", 1)                         = 1
read(4, "o", 1)                         = 1
read(4, "@", 1)                         = 1
read(4, "l", 1)                         = 1
read(4, "i", 1)                         = 1
read(4, "s", 1)                         = 1
read(4, "t", 1)                         = 1
read(4, "s", 1)                         = 1
read(4, ".", 1)                         = 1
read(4, "e", 1)                         = 1
read(4, "x", 1)                         = 1
read(4, "a", 1)                         = 1
read(4, "m", 1)                         = 1
read(4, "p", 1)                         = 1
read(4, "l", 1)                         = 1
read(4, "e", 1)                         = 1
read(4, ".", 1)                         = 1
read(4, "c", 1)                         = 1
read(4, "o", 1)                         = 1
read(4, "m", 1)                         = 1
read(4, "\n", 1)                        = 1
close(4)                                = 0

It does this for every file it touches as well as network connections it
reads from.
I don't know yet, how and why exactly it does it this way, but it seems
rather insane to me, so I think it might need some patches in order to
clean it up.

It turned out that attempting to subscribe someone to a mailing list
used 794 read(x, y, 1) style syscalls. I don't think I want to know how
often it calls read() in order to post a message to all members of the
list.
Maybe this could be solved by using getline(3) instead, which is in
POSIX.1-2008 and implemented on current versions of at least glibc,
FreeBSD, NetBSD and of course musl.
I will contact the mlmmj developers and try to resolve the issue.

Solar, maybe you should still wait a bit before switching openwall over
to mlmmj ;)

Best,
	Moritz


  reply	other threads:[~2011-08-16 13:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 17:08 Rich Felker
2011-06-27 21:16 ` Szabolcs Nagy
2011-06-27 21:19   ` Rich Felker
2011-06-27 21:38     ` Szabolcs Nagy
2011-06-27 21:37       ` Rich Felker
2011-06-27 21:43         ` Rich Felker
2011-06-29 14:19           ` Szabolcs Nagy
2011-06-29 19:27             ` Rich Felker
2011-06-29 20:03               ` Szabolcs Nagy
2011-08-16 13:03                 ` Moritz Wilhelmy [this message]
2011-08-16 13:06                   ` Rich Felker
2011-08-16 13:16                     ` Moritz Wilhelmy
2011-08-16 13:52                       ` Rich Felker

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=20110816130350.GF26140@barfooze.de \
    --to=ml+musl@wzff.de \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).