From: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
To: Moti Haimovsky <motih@mellanox.com>
Cc: ferruh.yigit@intel.com, stephen@networkplumber.org, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH V3 2/2] net/failsafe: convert to new Rx offloads API
Date: Mon, 15 Jan 2018 17:02:52 +0100 [thread overview]
Message-ID: <20180115160252.734ts4actt6wqrav@bidouze.vm.6wind.com> (raw)
In-Reply-To: <1515595223-36144-2-git-send-email-motih@mellanox.com>
My remarks for this one are mostly the same,
I will try to repeat them faithfully...
"convert to" -> "use"
On Wed, Jan 10, 2018 at 04:40:23PM +0200, Moti Haimovsky wrote:
...
> +static bool
> +fs_rxq_are_offloads_valid(struct rte_eth_dev *dev, uint64_t offloads)
function name can be shortened (s/_are//).
> +{
> + uint64_t port_offloads = dev->data->dev_conf.rxmode.offloads;
> + uint64_t queue_supp_offloads = PRIV(dev)->infos.rx_queue_offload_capa;
> + uint64_t port_supp_offloads = PRIV(dev)->infos.rx_offload_capa;
> +
Please separate variable definition and initialization.
> + if ((offloads & (queue_supp_offloads | port_supp_offloads)) !=
> + offloads)
> + return false;
> + /* Verify we have no conflict with port offloads */
> + if ((port_offloads ^ offloads) & port_supp_offloads)
> + return false;
> + return true;
> +}
> +
> static void
> fs_rx_queue_release(void *queue)
> {
> @@ -290,6 +313,17 @@
> fs_rx_queue_release(rxq);
> dev->data->rx_queues[rx_queue_id] = NULL;
> }
> + /* Verify application offloads are valid for our port and queue. */
> + if (!fs_rxq_are_offloads_valid(dev, rx_conf->offloads)) {
> + rte_errno = ENOTSUP;
> + ERROR("%p: Rx queue offloads 0x%lx don't match port "
Here, the device pointer should not be displayed.
It may be a larger issue with the fail-safe, that should be fixed (when
using multiple fail-safe instances), but for now, all outputs should
follow the same format.
Otherwise, use PRIx64 for displaying uint64_t.
> + "offloads 0x%lx or supported offloads 0x%lx",
> + (void *)dev, rx_conf->offloads,
> + dev->data->dev_conf.rxmode.offloads,
> + PRIV(dev)->infos.rx_offload_capa |
> + PRIV(dev)->infos.rx_queue_offload_capa);
> + return -rte_errno;
> + }
> rxq = rte_zmalloc(NULL,
> sizeof(*rxq) +
> sizeof(rte_atomic64_t) * PRIV(dev)->subs_tail,
> @@ -589,12 +623,16 @@
> sizeof(default_infos));
> } else {
> uint32_t rx_offload_capa;
> + uint32_t rxq_offload_capa;
>
> rx_offload_capa = default_infos.rx_offload_capa;
> + rxq_offload_capa = default_infos.rx_queue_offload_capa;
> FOREACH_SUBDEV_STATE(sdev, i, dev, DEV_PROBED) {
> rte_eth_dev_info_get(PORT_ID(sdev),
> &PRIV(dev)->infos);
> rx_offload_capa &= PRIV(dev)->infos.rx_offload_capa;
> + rxq_offload_capa &=
> + PRIV(dev)->infos.rx_queue_offload_capa;
> }
> sdev = TX_SUBDEV(dev);
> rte_eth_dev_info_get(PORT_ID(sdev), &PRIV(dev)->infos);
> --
> 1.8.3.1
>
Regards,
--
Gaëtan Rivet
6WIND
next prev parent reply other threads:[~2018-01-15 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 19:31 [dpdk-dev] [PATCH 0/2] net/failsafe: convert to new ethdev " Moti Haimovsky
2018-01-04 19:31 ` [dpdk-dev] [PATCH 1/2] net/failsafe: convert to new Tx " Moti Haimovsky
2018-01-04 19:50 ` [dpdk-dev] [PATCH V2 0/2] net/failsafe: convert to new ethdev " Moti Haimovsky
2018-01-04 19:50 ` [dpdk-dev] [PATCH V2 1/2] net/failsafe: convert to new Tx " Moti Haimovsky
2018-01-04 20:15 ` Stephen Hemminger
2018-01-10 14:40 ` [dpdk-dev] [PATCH V3 " Moti Haimovsky
2018-01-10 14:40 ` [dpdk-dev] [PATCH V3 2/2] net/failsafe: convert to new Rx " Moti Haimovsky
2018-01-15 16:02 ` Gaëtan Rivet [this message]
2018-01-15 15:57 ` [dpdk-dev] [PATCH V3 1/2] net/failsafe: convert to new Tx " Gaëtan Rivet
2018-01-17 14:30 ` [dpdk-dev] [PATCH v4 1/2] net/failsafe: use " Moti Haimovsky
2018-01-17 14:30 ` [dpdk-dev] [PATCH v4 2/2] net/failsafe: use new Rx " Moti Haimovsky
2018-01-17 17:30 ` [dpdk-dev] [PATCH v4 1/2] net/failsafe: use new Tx " Gaëtan Rivet
2018-01-17 19:24 ` Ferruh Yigit
2018-01-04 19:50 ` [dpdk-dev] [PATCH V2 2/2] net/failsafe: convert to new Rx " Moti Haimovsky
2018-01-04 19:31 ` [dpdk-dev] [PATCH " Moti Haimovsky
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=20180115160252.734ts4actt6wqrav@bidouze.vm.6wind.com \
--to=gaetan.rivet@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=motih@mellanox.com \
--cc=stephen@networkplumber.org \
/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).