From: David Miller <davem@davemloft.net>
To: jbaron@akamai.com
Cc: vyasevich@gmail.com, netdev@vger.kernel.org, kaber@trash.net
Subject: Re: macvlan: optimizing the receive path?
Date: Tue, 07 Oct 2014 14:49:25 -0400 (EDT) [thread overview]
Message-ID: <20141007.144925.1436185932073418204.davem@davemloft.net> (raw)
In-Reply-To: <5434246E.1000403@akamai.com>
From: Jason Baron <jbaron@akamai.com>
Date: Tue, 07 Oct 2014 13:35:42 -0400
> So if there are no objections, I will post as a formal patch.
No objections from me, thanks for all the info.
prev parent reply other threads:[~2014-10-07 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 20:28 macvlan: optimizing the receive path? Jason Baron
2014-10-02 21:31 ` Stephen Hemminger
2014-10-03 15:08 ` Jason Baron
2014-10-03 16:16 ` Vlad Yasevich
2014-10-05 0:42 ` David Miller
2014-10-06 13:04 ` Vlad Yasevich
2014-10-07 17:35 ` Jason Baron
2014-10-07 18:00 ` Eric Dumazet
2014-10-07 18:49 ` 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=20141007.144925.1436185932073418204.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jbaron@akamai.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=vyasevich@gmail.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).