From: Grant Grundler <iod00d@hp.com>
To: Michael Chan <mchan@broadcom.com>
Cc: Grant Grundler <iod00d@hp.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@oss.sgi.com
Subject: Re: [PATCH] tg3_msi() and weakly ordered memory
Date: Tue, 14 Jun 2005 11:04:25 -0700 [thread overview]
Message-ID: <20050614180425.GE24371@esmail.cup.hp.com> (raw)
In-Reply-To: <1118767397.7059.19.camel@rh4>
On Tue, Jun 14, 2005 at 09:43:17AM -0700, Michael Chan wrote:
...
> Something like:
>
> if (sblk->status_tag != tp->last_tag)
> clear_interrupt();
> netif_rx_schedule();
>
> This way we don't have to clear the SD_STATUS_UPDATED bit. I will
> experiment with this and see if it works well.
that sounds good - thanks.
> I don't think we are reading the index on every iteration. In tg3_rx(),
> we read it at the beginning before the loop, and one more time if we
> have caught up with the hw index before exiting the loop.
oh - sorry - my bad. Same is true for tg3_tx().
And I just noticed I'm smoking crack on "nested locks" too...
one is "lock" and the other is "tx_lock".
*sigh* - need more sleep.
> I mildly disagree. I think we should maximize the amount of work done in
> tg3_poll(). For example, reading the rx_producer index one more time
> when we have caught up with hw index before exiting the loop is a good
> thing IMO.
ok.
thanks,
grant
next prev parent reply other threads:[~2005-06-14 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B1508D50A0692F42B217C22C02D84972067F0804@NT-IRVA-0741.brcm.ad.broadcom.com>
2005-06-14 15:40 ` [PATCH] tg3_msi() and weakly ordered memory Grant Grundler
[not found] ` <1118767397.7059.19.camel@rh4>
2005-06-14 18:04 ` Grant Grundler [this message]
2005-06-14 17:55 ` Grant Grundler
[not found] <B1508D50A0692F42B217C22C02D84972067F0805@NT-IRVA-0741.brcm.ad.broadcom.com>
2005-06-14 15:46 ` Grant Grundler
[not found] ` <1118771563.7059.30.camel@rh4>
[not found] ` <20050614211530.GB25516@esmail.cup.hp.com>
2005-06-21 23:56 ` David S. Miller
2005-06-22 5:20 ` Grant Grundler
2005-06-14 3:37 Grant Grundler
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=20050614180425.GE24371@esmail.cup.hp.com \
--to=iod00d@hp.com \
--cc=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).