DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Dekel Peled <dekelp@mellanox.com>, Yongseok Koh <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Ori Kam <orika@mellanox.com>,
	Dekel Peled <dekelp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: allow port start with zero Rx queues
Date: Thu, 24 Jan 2019 11:14:52 +0000	[thread overview]
Message-ID: <AM0PR0502MB37953792525C20F3D3AD2E0FC39A0@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1548145315-37820-1-git-send-email-dekelp@mellanox.com>

Tuesday, January 22, 2019 10:22 AM, Dekel Peled:
> Subject: [dpdk-dev] [PATCH] net/mlx5: allow port start with zero Rx queues
> 
> During port start, function mlx5_ctrl_flow_vlan() is called to create default
> ingress flow rules.
> For specific use-cases, a port can be used for Tx only.
> In such case, number of Rx queues can be set to 0 to save resources, hence
> the default ingress rules are irrelevant.
> 
> This patch modifies function mlx5_ctrl_flow_vlan() to avoid the creation of
> the default ingress rules when number of Rx queues is 0.
> It also includes update of validation functions for relevant actions,
> mlx5_flow_validate_action_queue() and mlx5_flow_validate_action_rss(),
> to prevent creation of flow rules with these actions when number of Rx
> queues is 0.
> 
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>

Applied to next-net-mlx, thanks. 

      reply	other threads:[~2019-01-24 11:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22  8:21 Dekel Peled
2019-01-24 11:14 ` Shahaf Shuler [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=AM0PR0502MB37953792525C20F3D3AD2E0FC39A0@AM0PR0502MB3795.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=orika@mellanox.com \
    --cc=yskoh@mellanox.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).