From: Thomas Monjalon <thomas@monjalon.net>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: dev@dpdk.org, "Yang, Zhiyong" <zhiyong.yang@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"matan@mellanox.com" <matan@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add preferred burst size support
Date: Wed, 14 Feb 2018 17:31:59 +0100 [thread overview]
Message-ID: <10854628.KyNNLvJU2P@xps> (raw)
In-Reply-To: <5282475.QW617zM3In@xps>
> > > rte_eth_rx_burst(..,nb_pkts) function has semantic that if return value is
> > > smaller than requested, application can consider it end of packet stream.
> > > Some hardware can only support smaller burst sizes which need to be
> > > advertised. Similar is the case for Tx burst.
> > >
> > > This patch adds deprecation notice for rte_eth_dev_info structure as new
> > > members, for preferred Rx and Tx burst and ring size would be added -
> > > impacting the size of the structure.
> > >
> > > Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> > > Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> > > Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
> > > Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> >
> > Acked-by: Zhiyong Yang <zhiyong.yang@intel.com>
>
> Maybe that we want to re-use the same struct to define min, max
> and preferred sizes.
>
> For the global idea,
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
Applied
prev parent reply other threads:[~2018-02-14 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 12:44 [dpdk-dev] [PATCH] " Shreyansh Jain
2018-02-01 12:48 ` [dpdk-dev] [PATCH v2] " Shreyansh Jain
2018-02-01 12:52 ` Hemant Agrawal
2018-02-01 12:52 ` Andrew Rybchenko
2018-02-01 13:27 ` Bruce Richardson
2018-02-01 14:28 ` Shreyansh Jain
2018-02-01 14:19 ` Bruce Richardson
2018-02-05 5:39 ` Shreyansh Jain
2018-02-05 6:22 ` [dpdk-dev] [PATCH v3] " Shreyansh Jain
2018-02-05 6:17 ` Yang, Zhiyong
2018-02-13 23:55 ` Thomas Monjalon
2018-02-14 16:31 ` Thomas Monjalon [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=10854628.KyNNLvJU2P@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=konstantin.ananyev@intel.com \
--cc=matan@mellanox.com \
--cc=shreyansh.jain@nxp.com \
--cc=zhiyong.yang@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).