lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 29 Apr 2014 14:23:09 +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 Li [mailto:lznuaa@...il.com] > On Tue, Apr 29, 2014 at 9:01 AM, David Laight <David.Laight@...lab.com> wrote: > > 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! > > I think it is same thing. If I am wrong, please tell me difference. The ownership bit in the ring flags - that the hardware uses. Which are printed in the next field. I'm guessing that the reason the tx ring is 'interesting' is that there have been bugs where the driver and hardware disagree about which entry each should process next. Otherwise the full tx ring is likely to be very very boring. David
Powered by blists - more mailing lists