netdev - Re: RX/dropped counter values for tagged packets

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1364787794.5113.147.camel@edumazet-glaptop>
Date:	Sun, 31 Mar 2013 20:43:14 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Ani Sinha <linuxdev@...rban.org>
Cc:	Ani Sinha <ani@...stanetworks.com>, netdev@...r.kernel.org
Subject: Re: RX/dropped counter values for tagged packets

On Sun, 2013-03-31 at 20:17 -0700, Ani Sinha wrote:

> Correct. Now if you combine the two cases, we increment the rx count
> for tagged packets in  vlan_do_receive() and then in "another_round",
> if pt_prev is null, we also increment the rx_dropped.
> 

Thats the way its done in a NIC driver.

We increment rx_{bytes|packets} counters before giving the packet to the
upper stack.

Then the stack might drop the packet and increment rx_dropped.



--
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