DPDK patches and discussions
 help / color / mirror / Atom feed
From: Clarylin L <clearasu@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Unable to get multi-segment mbuf working for ixgbe
Date: Mon, 28 Mar 2016 10:05:40 -0700	[thread overview]
Message-ID: <CAKj5MjtR0qD3r3bG6JUbzO0SNSu4_4o+g1wwmN--KzjTdhYvjQ@mail.gmail.com> (raw)
In-Reply-To: <CAKj5MjtvX=1=Dka7_78_qNhRF_bUH_GaJvpT5WjUwrASTn3ZBg@mail.gmail.com>

Any pointers to what the issue could be? thanks

On Fri, Mar 25, 2016 at 4:13 PM, Clarylin L <clearasu@gmail.com> wrote:

> Hello,
>
> I am trying to use multi-segment mbuf to receive large packet. I enabled
> jumbo_frame and enable_scatter for the port and was expecting mbuf chaining
> would be used to receive packets larger than the mbuf size (which was set
> to 2048).
>
> When sending 3000-byte (without fragmentation) packet from another
> non-dpdk host, I didn't see packet was received by the ixgbe PMD driver.
>
> After a quick debugging session I found that the following statement in ixgbe_recv_scattered_pkts
> (ixgbe_rxtx.c) is
> always true and break the loop in case of large packet, while it's not the
> case for small packet (smaller than mbuf size):
>
> if (! staterr & rte_cpu_to_le32(IXGBE_RXDADV_STAT_DD))
>     break;
>
> Is enabling jumbo_frame and enable_scatter good enough to get started the
> mbuf chaining?
>
> Appreciate any input! Thanks.
>

  reply	other threads:[~2016-03-28 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25 23:13 Clarylin L
2016-03-28 17:05 ` Clarylin L [this message]
2016-03-29  9:24   ` 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=CAKj5MjtR0qD3r3bG6JUbzO0SNSu4_4o+g1wwmN--KzjTdhYvjQ@mail.gmail.com \
    --to=clearasu@gmail.com \
    --cc=dev@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).