From: "Michael Chan" <mchan@broadcom.com>
To: "Rick Jones" <rick.jones2@hp.com>
Cc: "David Miller" <davem@davemloft.net>,
jeff@garzik.org, "netdev" <netdev@vger.kernel.org>
Subject: Re: [PATCH 10/11][TG3]: Reduce spurious interrupts.
Date: Mon, 07 May 2007 11:41:17 -0700 [thread overview]
Message-ID: <1178563277.4859.77.camel@dell> (raw)
In-Reply-To: <463F656E.5060802@hp.com>
On Mon, 2007-05-07 at 10:44 -0700, Rick Jones wrote:
>
> Mostly I was thinking that not all PIO reads are the same "length" and so the
> effect of the PIO read will vary, perhaps considerably, with the platform,
> particularly for a very large NUMA platform.
>
Oh I see. If the PIO read is "long" on the platform, the performance
impact will be bigger. But it probably also means that it takes longer
for the write to get to the chip to de-assert the IRQ. Without the
read, it is therefore more likely to get an extra interrupt in such a
case.
prev parent reply other threads:[~2007-05-07 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 0:55 [PATCH 10/11][TG3]: Reduce spurious interrupts Michael Chan
2007-05-05 0:42 ` Jeff Garzik
2007-05-05 1:45 ` Michael Chan
2007-05-05 2:42 ` David Miller
2007-05-05 2:50 ` Michael Chan
2007-05-05 3:47 ` David Miller
2007-05-06 0:15 ` Michael Chan
2007-05-06 0:19 ` [PATCH revised 10/11][TG3]: Eliminate " Michael Chan
2007-05-07 7:26 ` David Miller
2007-05-06 0:21 ` [PATCH revised 11/11][TG3]: Update version and reldate Michael Chan
2007-05-07 7:26 ` David Miller
2007-05-07 16:39 ` [PATCH 10/11][TG3]: Reduce spurious interrupts Rick Jones
[not found] ` <1178562469.4859.70.camel@dell>
2007-05-07 17:44 ` Rick Jones
2007-05-07 18:41 ` Michael Chan [this message]
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=1178563277.4859.77.camel@dell \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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;
as well as URLs for NNTP newsgroup(s).