From: David Newall <davidn@davidnewall.com>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: David Miller <davem@davemloft.net>,
dmantipov@yandex.ru, linux-kernel@vger.kernel.org
Subject: Re: Are Linux pipes slower than the FreeBSD ones ?
Date: Wed, 05 Mar 2008 22:42:17 +1030 [thread overview]
Message-ID: <47CE8E21.2000309@davidnewall.com> (raw)
In-Reply-To: <47CE6C41.3090303@cosmosbay.com>
Eric Dumazet wrote:
> I tried the 'pipe' prog on a fresh linux-2.6.24.2, on a dual Xeon 5120
> machine, and we can notice that four cpus are used (but only two
> threads are running on this benchmark)
Do the threads migrate from CPU to CPU? That would be sub-optimal,
wouldn't it?
next prev parent reply other threads:[~2008-03-05 12:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 7:46 Are Linux pipes slower than the FreeBSD ones ? Antipov Dmitry
2008-03-05 8:00 ` David Miller
2008-03-05 9:47 ` Eric Dumazet
2008-03-05 10:19 ` Andi Kleen
2008-03-05 12:12 ` David Newall [this message]
2008-03-05 14:20 ` Nick Piggin
2008-03-05 14:55 ` Eric Dumazet
2008-03-05 15:38 ` Nick Piggin
2008-03-05 15:55 ` Ray Lee
2008-03-05 16:02 ` Nick Piggin
2008-03-06 12:11 ` Dmitry Antipov
2008-03-17 12:53 ` Nick Piggin
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=47CE8E21.2000309@davidnewall.com \
--to=davidn@davidnewall.com \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=dmantipov@yandex.ru \
--cc=linux-kernel@vger.kernel.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