DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Alex Markuze <alex@weka.io>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] segmented recv ixgbevf
Date: Thu, 30 Oct 2014 11:09:57 +0000	[thread overview]
Message-ID: <20141030110956.GA8456@bricha3-MOBL3> (raw)
In-Reply-To: <CAKfHP0Up34C7r6SgrdTt+p-yV0bRkoP=hg8MR1P-C6iEg+cX2Q@mail.gmail.com>

On Thu, Oct 30, 2014 at 12:23:09PM +0200, Alex Markuze wrote:
> Hi,
> I'm seeing an unwanted behaviour in the receive flow of ixgbevf. While
> using Jumbo frames and sending 4k+ bytes , the receive side breaks up the
> packets into 2K buffers, and I receive 3 mbuffs per packet.
> Im setting the .max_rx_pkt_len to 4.5K and the mempoll has 5K sized
> elements?
> Anything else I'm missing here. The purpose is to have all 4k+ bytes in one
> single continuous buffer.

That should be working, I think. 
Does it work with the plain ixgbe driver on the host? 
Is there anything in the output of the driver initialization saying something like "forcing scatter mode"?

  reply	other threads:[~2014-10-30 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 10:23 Alex Markuze
2014-10-30 11:09 ` Bruce Richardson [this message]
2014-10-30 12:48   ` Alex Markuze
2014-10-30 13:18     ` Bruce Richardson
2014-11-05 14:48     ` Matt Laswell

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141030110956.GA8456@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=alex@weka.io \
    --cc=dev@dpdk.org \


* 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).