From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Sunil Kumar Kori <skori@marvell.com>,
thomas@monjalon.net, arybchenko@solarflare.com,
wenzhuo.lu@intel.com, jingjing.wu@intel.com,
bernard.iremonger@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] app/testpmd: creating mbuf pool based on maximum supported segments
Date: Mon, 10 Jun 2019 18:45:22 +0100 [thread overview]
Message-ID: <837ff998-89f0-e7b2-3753-a89cc0e96480@intel.com> (raw)
In-Reply-To: <1558946129-5816-3-git-send-email-skori@marvell.com>
On 5/27/2019 9:35 AM, Sunil Kumar Kori wrote:
> Configuring buffer size based following parameters:
> - max-pkt-len
> - max supported segments per MTU
>
> Buffer size are configured as given below:
> - If platform supports infinite segments per packet then default
> buffer size is used.
> - If platform supports nb_mtu_seg_max segments then buffer size
> is configured as (max-pkt-len / nb_mtu_seg_max) + headroom
>
> Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-06-10 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 8:35 [dpdk-dev] [PATCH 0/2] Enabling default mbuf segments support Sunil Kumar Kori
2019-05-27 8:35 ` [dpdk-dev] [PATCH 1/2] lib/librte_ethdev: add in default value of rte_eth_dev_info Sunil Kumar Kori
2019-06-09 14:33 ` Andrew Rybchenko
2019-06-10 17:35 ` Ferruh Yigit
2019-06-14 5:31 ` Mo, YufengX
2019-06-14 16:51 ` Ferruh Yigit
2019-06-14 17:21 ` Ferruh Yigit
2019-06-17 1:38 ` Mo, YufengX
2019-05-27 8:35 ` [dpdk-dev] [PATCH 2/2] app/testpmd: creating mbuf pool based on maximum supported segments Sunil Kumar Kori
2019-06-10 17:45 ` Ferruh Yigit [this message]
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=837ff998-89f0-e7b2-3753-a89cc0e96480@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=skori@marvell.com \
--cc=thomas@monjalon.net \
--cc=wenzhuo.lu@intel.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).