From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] vlan: adds drops accounting
Date: Thu, 03 Sep 2009 20:11:31 -0700 (PDT) [thread overview]
Message-ID: <20090903.201131.194103894.davem@davemloft.net> (raw)
In-Reply-To: <4A9F9CD4.7040408@gmail.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 03 Sep 2009 12:39:16 +0200
> Its hard to tell if vlans are dropping frames, since
> every frame given to vlan_???_start_xmit() functions
> is accounted as fully transmitted by lower device.
>
> We can test dev_queue_xmit() return values to
> properly account for dropped frames.
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Applied.
But, how inappropriate would it be to keep doing the accounting
but pass the status back to the caller? Or will that screw up
the qdisc running engine?
next prev parent reply other threads:[~2009-09-04 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 10:39 [PATCH net-next-2.6] vlan: adds drops accounting Eric Dumazet
2009-09-04 3:11 ` David Miller [this message]
2009-09-04 11:59 ` Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090903.201131.194103894.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).