DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Karthikraj palanichamy <karthikraj.palanichamy@veryxtech.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] I350 jumbo frame transmission
Date: Wed, 12 Apr 2017 14:01:41 +0100	[thread overview]
Message-ID: <20170412130141.GA33412@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <58EE22B5.5040001@veryxtech.com>

On Wed, Apr 12, 2017 at 06:21:01PM +0530, Karthikraj palanichamy wrote:
> Hi,
> 
> I am using I350 card. The API rte_eth_dev_info_get() updated the parameter
> 'max_rx_pktlen' in 'struct rte_eth_dev_info' as 16384.
> 
> But when I try transmission with multiple segments, I could not transmit
> more than 9732 bytes.
> 
> I tried with testpmd and getting the same results.ie) couldn't transmit more
> than 9732 using testpmd.
> 
> Is this a limitation or am I missing anything?
> 
> Note : I tried with X540 card. I got 'max_rx_pktlen' as 15387 and I could
> transmit and receive upto 15387.
> 
> Thanks
> Karthik
>
It seems the info returned may be wrong. According to the i350
datasheet [1], table 1-2, the max frame size supported by the i350 is
9.5k which roughly tallies with what you are seeing.

Regards,
/Bruce

[1] http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/ethernet-controller-i350-datasheet.pdf

  parent reply	other threads:[~2017-04-12 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 12:51 Karthikraj palanichamy
2017-04-12 12:59 ` Karthikraj palanichamy
2017-04-12 13:01 ` Bruce Richardson [this message]
2017-04-12 13:04   ` Bruce Richardson

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=20170412130141.GA33412@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=karthikraj.palanichamy@veryxtech.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).