From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet 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 Message-ID: <1369441963.3301.459.camel@edumazet-glaptop> References: <064a09fffe48540b66a3ee503860ed9e8a1eb5f1.1369406826.git.tgraf@suug.ch> <1369421900.3301.431.camel@edumazet-glaptop> <1369432621.3301.445.camel@edumazet-glaptop> <1369434870.3301.452.camel@edumazet-glaptop> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Thomas Graf , netdev , "dev@openvswitch.org" To: Jesse Gross Return-path: Received: from mail-ob0-f169.google.com ([209.85.214.169]:61318 "EHLO mail-ob0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750757Ab3EYAcp (ORCPT ); Fri, 24 May 2013 20:32:45 -0400 Received: by mail-ob0-f169.google.com with SMTP id 16so5825266obc.14 for ; Fri, 24 May 2013 17:32:45 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: 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.