DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: bai bakari <912873551@qq.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] About the data payload of rte_mbuf?
Date: Thu, 6 Dec 2018 09:22:25 -0800	[thread overview]
Message-ID: <20181206092225.3702262e@xeon-e3> (raw)
In-Reply-To: <BC4196DE-7488-443D-9351-CD7F34D04586@intel.com>

On Thu, 6 Dec 2018 15:17:19 +0000
"Wiles, Keith" <keith.wiles@intel.com> wrote:

> > On Dec 6, 2018, at 12:09 AM, Stephen Hemminger <stephen@networkplumber.org> wrote:
> > 
> > On Thu, 6 Dec 2018 11:45:22 +0800
> > "bai bakari" <912873551@qq.com> wrote:
> >   
> >> when i send packets using dpdk-pktgen, i found:
> >> ip_len = 46
> >> ip_header_len = 20
> >> but the tcp_header_len=(tcp_hdr->data_off << 2)=0, 
> >> and (payload - (uint8_t *)ipv4_hdr) = 340 > ip_len.  
> > 
> > 
> > dpdk pktgen sends UDP not TCP.  
> 
> Not sure I understand this statement Pktgen can send UDP or TCP, it depends on the configuration. Does your statement mean Pktgen has a bug or what ?
> 
> Regards,
> Keith
> 

I just wanted to make sure that user had configured TCP, and not UDP>

      reply	other threads:[~2018-12-06 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06  3:45 bai bakari
2018-12-06  4:20 ` Varghese, Vipin
2018-12-06  4:59   ` bai bakari
2018-12-06  5:41     ` Varghese, Vipin
2018-12-06  5:48 ` Shyam Shrivastav
2018-12-06  5:52   ` Shyam Shrivastav
2018-12-06  6:19     ` [dpdk-dev] =?gb18030?b?u9i4tKO6ICBBYm91dCB0aGUgZGF0YSBwYXlsb2Fk?= =?gb18030?q?_of_rte=5Fmbuf=3F?=  =?gb18030?B?YmFpIGJha2FyaQ==?=
2018-12-06  7:09 ` [dpdk-dev] About the data payload of rte_mbuf? Stephen Hemminger
2018-12-06 15:17   ` Wiles, Keith
2018-12-06 17:22     ` Stephen Hemminger [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=20181206092225.3702262e@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=912873551@qq.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.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).