From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier MATZ Subject: Re: Regarding UDP checksum offload Date: Fri, 30 Jan 2015 10:15:48 +0100 Message-ID: <54CB4BC4.8060509@6wind.com> References: <54C8DDF3.2000802@6wind.com> <54C8FB95.7040503@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Prashant Upadhyaya 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, On 01/29/2015 01:56 PM, Prashant Upadhyaya wrote: > Another thing you can do is to retry on the latest stable dpdk which > is known to work (see csumonly.c in test-pmd). > > Let me add further, I am _just_ doing the UDP checksum offload > and not > the IP hdr checksum offload. I calculate and set IP header > checksum by > my own code. I hope that this is acceptable and does not > interfere with > UDP checksum offload > > > This should not be a problem. > > Indeed it worked with DPDK1.7 and then I retried with DPDK1.6 and it > worked there too. > Must have been some mistake at my end, may be I did not clean properly > when I was experimenting with some values of l2_len. > Sorry for the botheration to the list. > > While we are at it, a quick question -- in case I have an mbuf chain > whose payloads constitute a UDP packet, should I setup the ol_flags and > the l2_len, l3_len fields only in the first mbuf header of the chain or > in all the mbuf headers of the chain ? Only the first mbuf is required. This is the case for all offload infos like flags, tso, ... and it's the same in rx. Regards, Olivier