From: David Miller <davem@davemloft.net>
To: vyasevic@redhat.com
Cc: netdev@vger.kernel.org, mst@redhat.com
Subject: Re: [PATCH] macvtap: Do not double-count received packets
Date: Fri, 29 Nov 2013 16:07:46 -0500 (EST) [thread overview]
Message-ID: <20131129.160746.1842192161038812093.davem@davemloft.net> (raw)
In-Reply-To: <1385487432-17651-1-git-send-email-vyasevic@redhat.com>
From: Vlad Yasevich <vyasevic@redhat.com>
Date: Tue, 26 Nov 2013 12:37:12 -0500
> Currently macvlan will count received packets after calling each
> vlans receive handler. Macvtap attempts to count the packet
> yet again when the user reads the packet from the tap socket.
> This code doesn't do this consistently either. Remove the
> counting from macvap and let only macvlan count received
^^^^^^
--> macvtap
> packets.
>
> Signed-off-by: Vlad Yasevich <vyasevic@redhat.com>
Applied, with the above typo fixed, thanks.
prev parent reply other threads:[~2013-11-29 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 17:37 [PATCH] macvtap: Do not double-count received packets Vlad Yasevich
2013-11-26 21:09 ` Michael S. Tsirkin
2013-11-27 2:12 ` Jason Wang
2013-11-29 21:07 ` David Miller [this message]
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=20131129.160746.1842192161038812093.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.com \
/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).