DPDK-dev Archive on lore.kernel.org
 help / color / Atom feed
From: Sunil Kumar Kori <skori@marvell.com>
To: <thomas@monjalon.net>, <ferruh.yigit@intel.com>,
	<arybchenko@solarflare.com>, <wenzhuo.lu@intel.com>,
	<jingjing.wu@intel.com>, <bernard.iremonger@intel.com>
Cc: <dev@dpdk.org>, Sunil Kumar Kori <skori@marvell.com>
Subject: [dpdk-dev] [PATCH 0/2] Enabling default mbuf segments support
Date: Mon, 27 May 2019 14:05:27 +0530
Message-ID: <1558946129-5816-1-git-send-email-skori@marvell.com> (raw)

rte_eth_dev_info structure exposes, nb_seg_max & nb_mtu_seg_max to provide
maximum number of segments supported by the platform but API does not provide
any default value as well as no show case of above mentioned fields while
creating mbuf pool.

Also in absence of this, there may be a gap bewteen application configuration
and PMD capabilities.

Consider below mentioned points:
Point 1:
- PMD may support N or infinte segments. So no defined value is assigned to
  represent infinite value.

Point 2:
- PMD supports n segments at max and exposed the same to application.
- But application didn't created mbuf pool accoding to maximum supported segments
  so it may be that to support larger packet, application needs more segments than
  PMD's capability. So packet transmission operation may be discarded by the PMD.

Patch set implenments default value and their usage in testpmd to provide a show
case. It will help application to create mbuf pool with correct buffer size so
that application can cater all sized packets properly.

Sunil Kumar Kori (2):
  lib/librte_ethdev: add in default value of rte_eth_dev_info
  app/testpmd: creating mbuf pool based on maximum supported segments

 app/test-pmd/testpmd.c         | 21 +++++++++++++++++++++
 lib/librte_ethdev/rte_ethdev.c |  2 ++
 lib/librte_ethdev/rte_ethdev.h |  2 ++
 3 files changed, 25 insertions(+)

-- 
1.8.3.1


             reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27  8:35 Sunil Kumar Kori [this message]
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

Reply instructions:

You may reply publically 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=1558946129-5816-1-git-send-email-skori@marvell.com \
    --to=skori@marvell.com \
    --cc=arybchenko@solarflare.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jingjing.wu@intel.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

DPDK-dev Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/dpdk-dev/0 dpdk-dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dpdk-dev dpdk-dev/ https://lore.kernel.org/dpdk-dev \
		dev@dpdk.org dpdk-dev@archiver.kernel.org
	public-inbox-index dpdk-dev


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/ public-inbox