From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jesse Gross <jesse@nicira.com>
Cc: Thomas Graf <tgraf@suug.ch>, netdev <netdev@vger.kernel.org>,
"dev@openvswitch.org" <dev@openvswitch.org>
Subject: Re: [PATCH net-next 2/2] openvswitch: Use zerocopy if applicable when performing the upcall
Date: Fri, 24 May 2013 17:32:43 -0700 [thread overview]
Message-ID: <1369441963.3301.459.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAEP_g=_SCmqik=vOQeNF_z7VskG15rovBOLMFx6wPKru0CBDQQ@mail.gmail.com>
On Fri, 2013-05-24 at 17:08 -0700, Jesse Gross wrote:
> What's the alternative?
I guess Thomas was working on this ;)
We addressed all this on nfnetlink lately.
Presumably GSO stuff is a non issue for vSwitch upcalls.
But UDP messages can be big, and their checksum might be already
validated by the NIC.
next prev parent reply other threads:[~2013-05-25 0:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 14:52 [PATCH net-next 0/2] Open vSwitch zerocopy upcall Thomas Graf
2013-05-24 14:52 ` [PATCH net-next 1/2] net: Export skb_zerocopy() to zerocopy from one skb to another Thomas Graf
2013-05-24 15:31 ` Eric Dumazet
2013-05-24 16:01 ` Thomas Graf
2013-05-24 14:52 ` [PATCH net-next 2/2] openvswitch: Use zerocopy if applicable when performing the upcall Thomas Graf
2013-05-24 17:24 ` Jesse Gross
2013-05-24 18:58 ` Eric Dumazet
2013-05-24 21:23 ` Jesse Gross
2013-05-24 21:57 ` Eric Dumazet
2013-05-24 22:18 ` Jesse Gross
2013-05-24 22:34 ` Eric Dumazet
2013-05-25 0:08 ` Jesse Gross
2013-05-25 0:32 ` Eric Dumazet [this message]
2013-05-25 7:02 ` Thomas Graf
2013-05-25 14:39 ` Eric Dumazet
2013-05-27 1:28 ` Jesse Gross
2013-06-07 12:21 ` Thomas Graf
2013-06-10 20:34 ` Jesse Gross
2013-06-10 20:43 ` David Miller
2013-06-10 20:55 ` Jesse Gross
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=1369441963.3301.459.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=dev@openvswitch.org \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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