From: 陆秋文 <luqiuwen@gmail.com>
To: Victor Detoni <victordetoni@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] reassembly app doesn't send pkt
Date: Tue, 3 Jan 2017 15:34:30 +0800 [thread overview]
Message-ID: <CAH1gxTs=0mqM6j7TyZCht1u9jeW1cHfozGgtub43EiBbptK=Cw@mail.gmail.com> (raw)
In-Reply-To: <CANpwN=uK9OWn=Kpzoos9_EZRFrWVz8Z+9qm09yK8hiALuTOEpQ@mail.gmail.com>
Hi,
I have the same problem using 82599. When I sent a mbuf with multi-segment,
the 82599 driver's tx_burst fuction
will return 0, which means no packet sent.
I have no solution. Some 82599 NICs can send these packet successfully, but
some will fail.
?? I think this problem may related to vendor or firmware.
2016-11-12 21:29 GMT+08:00 Victor Detoni <victordetoni@gmail.com>:
> Hi,
>
> When I test ip_reassembly app on vmxnet3 nic works fine, but when I change
> to the nics 82599ES 10-Gigabit SFI/SFP+, it stop to send the packet
> "reassembled" on tx nic.
>
> when I remove the code bellow on rte_ipv4_reassembly.c source code, it
> sends pkt but truncated.
>
> rte_pktmbuf_chain(fp->frags[IP_FIRST_FRAG_IDX].mb, m);
>
> Anybody has some tip? I printed all functions like send_single_packet and
> send_burst and it seems Ok, when I compare ping pkt and udp frag pkt.
>
prev parent reply other threads:[~2017-01-03 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 13:29 Victor Detoni
2017-01-03 7:34 ` 陆秋文 [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='CAH1gxTs=0mqM6j7TyZCht1u9jeW1cHfozGgtub43EiBbptK=Cw@mail.gmail.com' \
--to=luqiuwen@gmail.com \
--cc=dev@dpdk.org \
--cc=victordetoni@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).