From: "Lazarenko, Vlad (WorldQuant)" <Vlad.Lazarenko@worldquant.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] When do we get non-contiguous mbufs from rte_eth_rx_burst?
Date: Thu, 9 Feb 2017 22:17:56 +0000 [thread overview]
Message-ID: <790E2AC11206AC46B8F4BB82078E34F80627DB12@EXUSMBX06.AD.MLP.com> (raw)
Hey everyone,
Does anyone happen to know if it is possible to receive non-contiguous mbufs from rte_eth_rx_burst? If so, when would this happen? I am thinking that NICs with LSO enabled could possibly do this if data does not fit into RTE_MBUF_DEFAULT_BUF_SIZE? But if the packet fits, I don't see why the driver could possibly split that across multiple mbufs. Any insight is highly appreciated.
Thanks,
Vlad
###################################################################################
The information contained in this communication is confidential, may be
subject to legal privilege, and is intended only for the individual named.
If you are not the named addressee, please notify the sender immediately and
delete this email from your system. The views expressed in this email are
the views of the sender only. Outgoing and incoming electronic communications
to this address are electronically archived and subject to review and/or disclosure
to someone other than the recipient.
###################################################################################
next reply other threads:[~2017-02-09 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 22:17 Lazarenko, Vlad (WorldQuant) [this message]
2017-02-09 22:35 ` Stephen Hemminger
2017-02-10 16:20 ` Lazarenko, Vlad (WorldQuant)
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=790E2AC11206AC46B8F4BB82078E34F80627DB12@EXUSMBX06.AD.MLP.com \
--to=vlad.lazarenko@worldquant.com \
--cc=users@dpdk.org \
/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).