From: Christoph Hellwig <hch@caldera.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.10pre7aa1
Date: Sun, 16 Sep 2001 21:04:21 +0200 [thread overview]
Message-ID: <20010916210421.A32343@caldera.de> (raw)
In-Reply-To: <20010910210607.C715@athlon.random> <Pine.LNX.4.33L.0109161359040.9536-100000@imladris.rielhome.conectiva> <20010916192316.A13248@athlon.random>
In-Reply-To: <20010916192316.A13248@athlon.random>; from andrea@suse.de on Sun, Sep 16, 2001 at 07:23:16PM +0200
On Sun, Sep 16, 2001 at 07:23:16PM +0200, Andrea Arcangeli wrote:
> > I can't quite remember if it was Linus or Larry who said:
> >
> > "Threads are for people who don't understand state machines"
> >
> >
> > If you cannot make your code clean without adding another
> > thread, it's probably a bad sign ;)
>
> Ask yourself why libaio in glibc uses threads.
Because glibc always uses the more bloated appropeach if there is a choice?
/me runs
> When there's no async-io
> hook you have no choice. Adding the hook is an advantage if you're going
> to use it during production, much better than
> rescheduling/creating/destroying various threads during production, but
> if you only need to register the hook once per day you'd waste time all
> the production time checking if somebody is registered in the hook.
I'd really like to see Ben's worktodo's in 2.4 - they are usefull even
without his whole asynchio framework and don't need big kernel changes..
Christoph
--
Whip me. Beat me. Make me maintain AIX.
next prev parent reply other threads:[~2001-09-16 19:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010910175416.A714@athlon.random>
2001-09-10 17:41 ` 2.4.10pre7aa1 Christoph Hellwig
2001-09-10 18:03 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-10 18:49 ` 2.4.10pre7aa1 Christoph Hellwig
2001-09-10 19:01 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-10 19:03 ` 2.4.10pre7aa1 Christoph Hellwig
2001-09-10 19:08 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-10 18:52 ` 2.4.10pre7aa1 Christoph Hellwig
2001-09-10 19:06 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-16 17:00 ` 2.4.10pre7aa1 Rik van Riel
2001-09-16 17:23 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-16 17:34 ` 2.4.10pre7aa1 Rik van Riel
2001-09-16 18:16 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-16 19:04 ` Christoph Hellwig [this message]
2001-09-12 8:24 ` 2.4.10pre7aa1 Rusty Russell
2001-09-17 9:13 2.4.10pre7aa1 Dipankar Sarma
-- strict thread matches above, loose matches on Subject: below --
2001-09-12 11:04 2.4.10pre7aa1 Dipankar Sarma
2001-09-12 14:03 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-12 14:42 ` 2.4.10pre7aa1 Dipankar Sarma
2001-09-12 14:53 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-16 12:23 ` 2.4.10pre7aa1 Rusty Russell
2001-09-11 13:05 2.4.10pre7aa1 Dipankar Sarma
2001-09-11 13:56 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-11 14:27 ` 2.4.10pre7aa1 Dipankar Sarma
2001-09-11 12:22 2.4.10pre7aa1 Dipankar Sarma
2001-09-11 11:53 2.4.10pre7aa1 Dipankar Sarma
2001-09-11 11:57 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-11 9:39 2.4.10pre7aa1 Maneesh Soni
2001-09-11 11:12 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-11 8:51 2.4.10pre7aa1 Dipankar Sarma
2001-09-11 11:04 ` 2.4.10pre7aa1 Andrea Arcangeli
2001-09-11 12:40 ` 2.4.10pre7aa1 Alan Cox
2001-09-11 13:49 ` 2.4.10pre7aa1 Andrea Arcangeli
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=20010916210421.A32343@caldera.de \
--to=hch@caldera.de \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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