netdev
[Top] [All Lists]

Re: [PATCH] tg3_msi() and weakly ordered memory

To: Michael Chan <mchan@xxxxxxxxxxxx>
Subject: Re: [PATCH] tg3_msi() and weakly ordered memory
From: Grant Grundler <iod00d@xxxxxx>
Date: Tue, 14 Jun 2005 08:46:25 -0700
Cc: "David S. Miller" <davem@xxxxxxxxxxxxx>, iod00d@xxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <B1508D50A0692F42B217C22C02D84972067F0805@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <B1508D50A0692F42B217C22C02D84972067F0805@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Jun 13, 2005 at 11:54:23PM -0700, Michael Chan wrote:
> > Once you write "0x1" to the mailbox register, the device stops
> > updating the status block and stops generating interrupts.
> > 
> > That is what makes a lot of things safe.
> 
> Only interrupts are stopped, status block will still be updated subject to
> during-ints coalescing.

Will setting during-ints to a very high threshhold essentially allow
us to "indefinitely" process stuff without taking any interrupts?
Would the threshhold counter get reset every time we write back
the status tag WITHOUT re-enableing interrupts?

If not, I suspect the CPU will circulate in tg3_poll until during-ints
is exhausted and DMA will stop until CPU reenables interrupts.
ie not until it's done processing outstanding packets.

thanks,
grant

<Prev in Thread] Current Thread [Next in Thread>