From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier MATZ Subject: Re: two tso related questions Date: Wed, 17 Dec 2014 14:02:03 +0100 Message-ID: <54917ECB.3080404@6wind.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "dev-VfR2kkLFssw@public.gmane.org" To: Helmut Sim , Alex Markuze Return-path: In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" Hi Helmut, On 12/17/2014 08:17 AM, Helmut Sim wrote: >>>>> While working on TSO based solution I faced the following two questions: >>>>> >>>>> 1. >>>>> is there a maximum pkt_len to be used with TSO?, e.g. let's say if >>>>> seg_sz >>>>> is 1400 can the entire segmented pkt be 256K (higer than 64K) ?, then >>>>> the >>>>> driver gets a list of chanined mbufs while the first mbuf is set to TSO >>>>> offload. I think the limitations depend on: - the window size advertised by the peer: your stack should handle this and not generate more packets that what the peer can receive - the driver: on ixgbe, the maximum payload length is 2^18. I don't know if there is a limitation on number of chained descriptors. I think we should define a way to know this limitation in the API. Maybe a comment saying that the TSO length should not be higher than 256KB (or fix it to 64KB in case future drivers do not support 256KB) is enough. Regards, Olivier