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: Mon, 14 May 2012 18:25:55 -0300 From: Marcelo Leitner <mleitner@...hat.com> To: netdev <netdev@...r.kernel.org> Subject: Question about be2net error field, rx_drops_no_pbuf Hi, What does 'rx_drops_no_pbuf' mean at be2net driver? I can see it is a hardware counter for some type of error, which I would like to know about. What causes it? All documentation I could find about it is a comment referring firmware specification: struct be_rxf_stats_v0 { struct be_port_rxf_stats_v0 port[2]; u32 rx_drops_no_pbuf; /* dword 132*/ ... } struct be_rxf_stats_v1 { struct be_port_rxf_stats_v1 port[4]; u32 rsvd0[2]; u32 rx_drops_no_pbuf; ... } That, plus this: be_get_stats64() { ... /* receiver fifo overrun */ /* drops_no_pbuf is no per i/f, it's per BE card */ stats->rx_fifo_errors = drvs->rxpp_fifo_overflow_drop + drvs->rx_input_fifo_overflow_drop + drvs->rx_drops_no_pbuf; return stats; } Thanks, Marcelo. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists