From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesper Dangaard Brouer Subject: Re: Questions on XDP Date: Wed, 22 Feb 2017 22:59:24 +0100 Message-ID: <20170222225924.59cdd82c@redhat.com> References: <58A8DD34.5040205@gmail.com> <20170221031829.GA3960@ast-mbp.thefacebook.com> <58ABB66D.60902@gmail.com> <20170221075523.GA29348@ast-mbp.thefacebook.com> <58ADC5A5.7020408@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Alexander Duyck , Alexei Starovoitov , Eric Dumazet , Netdev , Tom Herbert , Alexei Starovoitov , John Fastabend , Daniel Borkmann , David Miller , brouer@redhat.com To: John Fastabend Return-path: Received: from mx1.redhat.com ([209.132.183.28]:59100 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754455AbdBVWAw (ORCPT ); Wed, 22 Feb 2017 17:00:52 -0500 In-Reply-To: <58ADC5A5.7020408@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 22 Feb 2017 09:08:53 -0800 John Fastabend wrote: > > GSO/TSO is getting into advanced stuff I would rather not have to get > > into right now. I figure we need to take this portion one step at a > > time. To support GSO we need more information like the mss. > > > > Agreed lets get the driver support for basic things first. But this > is on my list. I'm just repeating myself but VM to VM performance uses > TSO/LRO heavily. Sorry, but I get annoyed every time I hear we need to support TSO/LRO/GRO for performance reasons. If you take one step back, you are actually saying we need bulking for better performance. And the bulking you are proposing is a TCP protocol specific bulking mechanism. I'm saying is let's make bulking protocol agnostic, by doing it at the packet level. And once the bulk enters the VM, by-all-means it should construct a GRO packet it can send into it's own network stack. -- Best regards, Jesper Dangaard Brouer MSc.CS, Principal Kernel Engineer at Red Hat LinkedIn: http://www.linkedin.com/in/brouer