From: Nikhil Agarwal <nikhil.agarwal@linaro.org>
To: <dev@dpdk.org>
Cc: <david.hunt@intel.com>, <nikhil.agarwal@nxp.com>,
<hemant.agrawal@nxp.com>, <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH 2/3] net/dpaa: implement max burst size in dev info
Date: Tue, 12 Dec 2017 15:35:19 +0530 [thread overview]
Message-ID: <20171212100520.20502-2-nikhil.agarwal@linaro.org> (raw)
In-Reply-To: <20171212100520.20502-1-nikhil.agarwal@linaro.org>
Signed-off-by: Nikhil Agarwal <nikhil.agarwal@linaro.org>
---
drivers/net/dpaa/dpaa_ethdev.c | 1 +
drivers/net/dpaa/dpaa_ethdev.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/net/dpaa/dpaa_ethdev.c b/drivers/net/dpaa/dpaa_ethdev.c
index cf5a2ec..79c6cc4 100644
--- a/drivers/net/dpaa/dpaa_ethdev.c
+++ b/drivers/net/dpaa/dpaa_ethdev.c
@@ -242,6 +242,7 @@ static void dpaa_eth_dev_info(struct rte_eth_dev *dev,
dev_info->max_tx_queues = dpaa_intf->nb_tx_queues;
dev_info->min_rx_bufsize = DPAA_MIN_RX_BUF_SIZE;
dev_info->max_rx_pktlen = DPAA_MAX_RX_PKT_LEN;
+ dev_info->max_burst_size = DPAA_MAX_BURST_SIZE;
dev_info->max_mac_addrs = DPAA_MAX_MAC_FILTER;
dev_info->max_hash_mac_addrs = 0;
dev_info->max_vfs = 0;
diff --git a/drivers/net/dpaa/dpaa_ethdev.h b/drivers/net/dpaa/dpaa_ethdev.h
index 5457d61..0400dce 100644
--- a/drivers/net/dpaa/dpaa_ethdev.h
+++ b/drivers/net/dpaa/dpaa_ethdev.h
@@ -64,6 +64,7 @@
#define DPAA_MIN_RX_BUF_SIZE 512
#define DPAA_MAX_RX_PKT_LEN 10240
+#define DPAA_MAX_BURST_SIZE 16
/* RX queue tail drop threshold
* currently considering 32 KB packets.
--
2.7.4
next prev parent reply other threads:[~2017-12-12 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 10:05 [dpdk-dev] [PATCH 1/3] ethdev: add max burst size to device info Nikhil Agarwal
2017-12-12 10:05 ` Nikhil Agarwal [this message]
2017-12-12 10:05 ` [dpdk-dev] [PATCH 3/3] examples/l3fwd-power: use device max burst size Nikhil Agarwal
2017-12-12 10:45 ` [dpdk-dev] [PATCH 1/3] ethdev: add max burst size to device info Matan Azrad
2017-12-12 11:03 ` Ananyev, Konstantin
2017-12-12 13:43 ` Shreyansh Jain
2017-12-13 12:52 ` Ananyev, Konstantin
2017-12-13 15:22 ` Shreyansh Jain
2018-05-22 22:17 ` Thomas Monjalon
2019-04-05 14:55 ` Ferruh Yigit
2019-04-05 14:55 ` Ferruh Yigit
2019-04-05 14:57 ` Yigit, Ferruh
2019-04-05 14:57 ` Yigit, Ferruh
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=20171212100520.20502-2-nikhil.agarwal@linaro.org \
--to=nikhil.agarwal@linaro.org \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=nikhil.agarwal@nxp.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).