All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Boris Pismenny <borisp-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ronye-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
	matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
	aviadye-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
	alexr-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [RFC 1/2] Introduce egress IB flow steering flag
Date: Thu, 20 Apr 2017 20:48:09 +0300	[thread overview]
Message-ID: <20170420174809.GS14088@mtr-leonro.local> (raw)
In-Reply-To: <8539540c4130ea91bbd128f2ec2845082d6000f8.1492685328.git.borisp-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]

On Thu, Apr 20, 2017 at 02:00:09PM +0300, Boris Pismenny wrote:
> From: borisp <borisp-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
>
> This commit introduces egress flow steering. Egress flow steering
> is useful for specifying actions that might be applied by hardware
> to outgoing flows on a specific QP.
>

How will user know which flow actions are applicable for egress traffic,
for both ingress/egress and for ingress only?

I think separate structure for ingress vs. egress are better approach,
than blind global flag.


> Signed-off-by: borisp <borisp-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

Please configure your git, "Signed-off-by" line is a legal document and
supposed to have proper author name.

Thanks

> ---
>  include/rdma/ib_verbs.h | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h
> index 99e4423..6c1c867 100644
> --- a/include/rdma/ib_verbs.h
> +++ b/include/rdma/ib_verbs.h
> @@ -1679,7 +1679,8 @@ enum ib_flow_domain {
>
>  enum ib_flow_flags {
>  	IB_FLOW_ATTR_FLAGS_DONT_TRAP = 1UL << 1, /* Continue match, no steal */
> -	IB_FLOW_ATTR_FLAGS_RESERVED  = 1UL << 2  /* Must be last */
> +	IB_FLOW_ATTR_FLAGS_EGRESS = 1UL << 2, /* Egress steering rule */
> +	IB_FLOW_ATTR_FLAGS_RESERVED  = 1UL << 3  /* Must be last */
>  };
>
>  struct ib_flow_eth_filter {
> --
> 1.8.3.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-04-20 17:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 11:00 [RFC 0/2] IB/core: Add ESP Crypto Flow Steering support Boris Pismenny
     [not found] ` <cover.1492685328.git.borisp-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-04-20 11:00   ` [RFC 1/2] Introduce egress IB flow steering flag Boris Pismenny
     [not found]     ` <8539540c4130ea91bbd128f2ec2845082d6000f8.1492685328.git.borisp-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-04-20 17:48       ` Leon Romanovsky [this message]
     [not found]         ` <20170420174809.GS14088-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-04-20 18:31           ` Boris Pismenny
2017-04-20 11:00   ` [RFC 2/2] IB/core: ESP AES-GCM crypto offload action Boris Pismenny
2017-04-20 15:16   ` [RFC 0/2] IB/core: Add ESP Crypto Flow Steering support Steve Wise
2017-04-20 15:24     ` Boris Pismenny
     [not found]       ` <DB6PR05MB3176852A5F283F850E37DA70B01B0-HESHCvp+V+r3UGwzQMMk6dqRiQSDpxhJvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-04-20 17:02         ` Jason Gunthorpe
     [not found]           ` <20170420170233.GA6275-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-04-20 17:15             ` Boris Pismenny

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=20170420174809.GS14088@mtr-leonro.local \
    --to=leonro-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=alexr-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=aviadye-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=borisp-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=ronye-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.