From: Olivier MATZ <olivier.matz@6wind.com>
To: Prashant Upadhyaya <praupadhyaya@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Regarding UDP checksum offload
Date: Fri, 30 Jan 2015 10:15:48 +0100 [thread overview]
Message-ID: <54CB4BC4.8060509@6wind.com> (raw)
In-Reply-To: <CAPBAu3V6Dwt=MTauBpBU9QxySk4Rj6n5ARZ4PsvZujWQe3w1ew@mail.gmail.com>
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
prev parent reply other threads:[~2015-01-30 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 11:25 Prashant Upadhyaya
2015-01-28 13:02 ` Olivier MATZ
2015-01-28 14:57 ` Prashant Upadhyaya
2015-01-28 15:09 ` Olivier MATZ
2015-01-29 12:56 ` Prashant Upadhyaya
2015-01-30 9:15 ` Olivier MATZ [this message]
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=54CB4BC4.8060509@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=praupadhyaya@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).