From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Mark <musicman529@yahoo.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS mkfs/mount options
Date: Tue, 17 Jun 2008 08:27:46 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0806170827400.32440@p34.internal.lan> (raw)
In-Reply-To: <153266.85236.qm@web34501.mail.mud.yahoo.com>
How did you tune your IRQ delivery?
Justin.
On Tue, 17 Jun 2008, Mark wrote:
> --- On Tue, 6/17/08, Dave Chinner <david@fromorbit.com> wrote:
>
>>> For each of these kernel threads, only those on CPU #2
>> are actually pulling notable load. Why is this?
>>
>> Because your disk interrupts are delivered to that CPU
>> only.
>
> Thank you! Tuning my IRQ delivery gave a noticeable speed-up.
>
> --
> Mark
>
> "What better place to find oneself than
> on the streets of one's home village?"
> --Capt. Jean-Luc Picard, "Family"
>
>
next prev parent reply other threads:[~2008-06-17 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 9:20 XFS mkfs/mount options Mark
2008-06-17 12:27 ` Justin Piszcz [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-17 17:29 Mark
2008-06-17 20:41 ` Martin Steigerwald
2008-06-17 7:33 Mark
2008-06-17 7:41 ` Dave Chinner
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=alpine.DEB.1.10.0806170827400.32440@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=musicman529@yahoo.com \
--cc=xfs@oss.sgi.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox