[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D0F701524@AcuExch.aculab.com>
Date: Tue, 29 Apr 2014 14:01:54 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Frank Li' <lznuaa@...il.com>
CC: Frank Li <Frank.Li@...escale.com>,
"shawn.guo@...aro.org" <shawn.guo@...aro.org>,
"B38611@...escale.com" <B38611@...escale.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"rmk+kernel@....linux.org.uk" <rmk+kernel@....linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH net-next 5/7] net:fec: add support for dumping transmit
ring on timeout
From: Frank ...
> > You probably want the read and write indexes as well.
>
> bdp == fep->cur_tx ? 'S' : ' ',
> bdp == fep->dirty_tx ? 'H' : ' ',
>
> Above code already print read and write index. 'S', 'H'
Gah I must be asleep!
Something made be think that was to do with the ring ownership bit!
David
Powered by blists - more mailing lists