From: Stephen Hemminger <stephen@networkplumber.org>
To: Dharmesh Mehta <mehtadharmesh@yahoo.com>
Cc: Users <users@dpdk.org>
Subject: Re: [dpdk-users] Fails to receive data more than 1500 bytes.
Date: Thu, 24 Aug 2017 16:18:31 -0700 [thread overview]
Message-ID: <20170824161831.2967997e@xeon-e3> (raw)
In-Reply-To: <1098935201.614169.1503613167623@mail.yahoo.com>
On Thu, 24 Aug 2017 22:19:27 +0000 (UTC)
Dharmesh Mehta <mehtadharmesh@yahoo.com> wrote:
> Hello,
> I am using Intel i350 NIC card, and I am not able to receive data more than 1500 bytes in a packet. I tried igb_uio as well as uio_pci_generic driver, but both fails.
> If I reduce data <= 1500 bytes than it works, but any thing more than 1500 is not able to receive.
> Do I have to tune any config parameter in order to support more than 1500?
> I tried to set MTU from code using API - rte_eth_dev_set_mtu(port_id, mtu) , but no success.
> 0000:03:00.0 'I350 Gigabit Network Connection 1521' drv=igb_uio unused=vfio-pci,uio_pci_generic0000:03:00.1 'I350 Gigabit Network Connection 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci0000:03:00.2 'I350 Gigabit Network Connection 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci0000:03:00.3 'I350 Gigabit Network Connection 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci
> Thanks in advance.DM.
In order to support >1500 bytes, you need to at least:
1. set jumbo_frame when setting rxmode
2. set enable_scatter in rxmode (unless mtu + overhead < pool size)
3. make sure pool mbuf size > eth->min_rx_buf_size
next prev parent reply other threads:[~2017-08-24 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1098935201.614169.1503613167623.ref@mail.yahoo.com>
2017-08-24 22:19 ` Dharmesh Mehta
2017-08-24 23:18 ` Stephen Hemminger [this message]
2017-08-25 0:01 ` Dharmesh Mehta
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=20170824161831.2967997e@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=mehtadharmesh@yahoo.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).