From: David Mosberger <davidm@napali.hpl.hp.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Linus Torvalds <torvalds@osdl.org>,
"Luck, Tony" <tony.luck@intel.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pipe performance regression on ia64
Date: Wed, 19 Jan 2005 05:11:18 +0000 [thread overview]
Message-ID: <16877.60406.192245.106565@napali.hpl.hp.com> (raw)
In-Reply-To: <41ED9D06.1070301@yahoo.com.au>
>>>>> On Wed, 19 Jan 2005 10:34:30 +1100, Nick Piggin <nickpiggin@yahoo.com.au> said:
Nick> David I remember you reporting a pipe bandwidth regression,
Nick> and I had a patch for it, but that hurt other workloads, so I
Nick> don't think we ever really got anywhere. I've recently begun
Nick> having another look at the multiprocessor balancer, so
Nick> hopefully I can get a bit further with it this time.
While it may be worthwhile to improve the scheduler, it's clear that
there isn't going to be a trivial "fix" for this issue, especially
since it's not even clear that anything is really broken. Independent
of the scheduler work, it would be very useful to have a pipe
benchmark which at least made the dependencies on the scheduler
obvious. So I think improving the scheduler and improving the LMbench
pipe benchmark are entirely complementary.
--david
next prev parent reply other threads:[~2005-01-19 5:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 17:41 pipe performance regression on ia64 Luck, Tony
2005-01-18 18:11 ` Linus Torvalds
2005-01-18 18:31 ` David Mosberger
2005-01-18 20:17 ` Linus Torvalds
2005-01-19 3:05 ` [Lmbench-users] " Larry McVoy
2005-01-19 3:20 ` Linus Torvalds
2005-01-19 3:24 ` Zou, Nanhai
2005-01-19 6:35 ` Luck, Tony
2005-01-19 9:23 ` Staelin, Carl
2005-01-19 16:40 ` Larry McVoy
2005-01-18 23:34 ` Nick Piggin
2005-01-19 5:11 ` David Mosberger [this message]
2005-01-19 12:43 ` Nick Piggin
2005-01-19 17:31 ` David Mosberger
2005-01-19 12:52 ` Ingo Molnar
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=16877.60406.192245.106565@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=tony.luck@intel.com \
--cc=torvalds@osdl.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