From: Stephen Hemminger <stephen@networkplumber.org>
To: Chaoyong He <chaoyong.he@corigine.com>
Cc: dev@dpdk.org, oss-drivers@corigine.com, Long Wu <long.wu@corigine.com>
Subject: Re: [PATCH] examples/l3fwd: support setting the data size of mbuf
Date: Wed, 16 Oct 2024 08:02:42 -0700 [thread overview]
Message-ID: <20241016080242.12c75c2c@hermes.local> (raw)
In-Reply-To: <20241016082232.4005800-1-chaoyong.he@corigine.com>
On Wed, 16 Oct 2024 16:22:32 +0800
Chaoyong He <chaoyong.he@corigine.com> wrote:
> From: Long Wu <long.wu@corigine.com>
>
> The previous code used a macro as the data size for mbuf
> to create the mempool and users cannot modify the size.
>
> Now modify the code to support setting the data size of
> mbuf by '--mbuf-size' parameter. If user does not add the
> parameter in start command line, the default size is still
> 'RTE_MBUF_DEFAULT_BUF_SIZE'.
>
> Examples:
> dpdk-l3fwd -l 0-3 -- -p 0x03 --mbuf-size=4096
>
> Signed-off-by: Long Wu <long.wu@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
Why not automatically determine the mbuf size based on mtu?
Would be more natural.
L3fwd functions as a test program and often used as a starting
point for best practices for doing new applications.
next prev parent reply other threads:[~2024-10-16 15:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 8:22 [PATCH] examples/l3fwd: support setting the data size of mbuf Chaoyong He
2024-10-16 9:05 ` Morten Brørup
2024-10-16 15:02 ` Stephen Hemminger [this message]
2024-10-16 21:17 ` Patrick Robb
2024-10-17 19:12 ` Stephen Hemminger
2024-10-18 2:42 ` [PATCH v2] " Chaoyong He
2024-10-18 2:50 ` lihuisong (C)
2024-10-18 2:59 ` Stephen Hemminger
2024-10-18 3:21 ` Chaoyong He
2024-10-18 3:42 ` Stephen Hemminger
2024-10-18 5:50 ` Chaoyong He
2024-10-18 15:59 ` Stephen Hemminger
2024-10-21 2:00 ` Chaoyong He
2024-10-21 17:07 ` Stephen Hemminger
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=20241016080242.12c75c2c@hermes.local \
--to=stephen@networkplumber.org \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=long.wu@corigine.com \
--cc=oss-drivers@corigine.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.