DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Clarylin L <clearasu@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] multi-segment mbuf
Date: Tue, 22 Mar 2016 10:27:40 +0000	[thread overview]
Message-ID: <20160322102740.GC19268@bricha3-MOBL3> (raw)
In-Reply-To: <CAKj5MjvwNx9rU-hp_-bpAKss4NVmDM7EAe6WOFJLjSO-UD--kA@mail.gmail.com>

On Mon, Mar 21, 2016 at 04:34:50PM -0700, Clarylin L wrote:
> I am trying multi-segment mbuf, but it seems not working.
> 
> On my target host, the mbuf size is set to 2048 and I am trying to send
> large packet to it (say 2500 bytes without fragmentation) from another
> host. I enabled both jumbo_frame and enable_scatter for the port. But I saw
> on the target only one mbuf is received with data_len equal to 2500 (it's
> supposed to be a two-mbuf chain).  Although mbuf itself is not working as
> expected, ping between two hosts succeeded (large ping size; no
> fragmentation).
> 
> 1. my mbuf size is only 2048. how can it support receiving such large
> packet in one mbuf?
> 
> 2.how to make it work as expected (enable multi-segment mbuf and receive
> using mbuf chain when needed)?
> 
> Appreciate your help.

Hi,

when you get the single mbuf with data_len == 2500, what is the buf_len value
reported as?

/Bruce

  reply	other threads:[~2016-03-22 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 23:34 Clarylin L
2016-03-22 10:27 ` Bruce Richardson [this message]
2016-03-22 20:36   ` Clarylin L
2016-03-22 22:13     ` Stephen Hemminger
2016-03-22 22:42       ` Clarylin L
2016-03-22 22:58       ` Clarylin L

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=20160322102740.GC19268@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=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).