Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Matan Barak <matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Yann Droneaud <ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>,
	Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>,
	Igor Ivanov <Igor.Ivanov-wN0M4riKYwLQT0dZR+AlfA@public.gmane.org>,
	Hadar Hen Zion <hadarh-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] An improved infrastructure for uverbs commands (My take at designing extensible scheme)
Date: Tue, 1 Oct 2013 14:43:11 +0300	[thread overview]
Message-ID: <524AB54F.9050205@mellanox.com> (raw)
In-Reply-To: <524AAAE6.3040508-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

On 1/10/2013 1:58 PM, Or Gerlitz wrote:
> On 24/09/2013 19:16, Yann Droneaud wrote:
>> PS: I haven't tested the create_flow() commands, (hopefully)
>> there's no libibverbs support yet for the new commands for the moment.
>> I will try to provide patches to improve create_flow()/destroy_flow()
>> and the way its data structures are expressed.
> Yan, nice doing! I am not sure to follow your last comment, this patch
> do touch
> ib_uverbs_create_flow and ib_uverbs_destroy_flow, what else remains to
> do there?
>
> Also, to help acceptance of the patch, could you please re-send it with
> removing all
> the references to emails and the hemisphere summer comment into the
> section below the
> "---"  line at the end of the git formatted patch header? they are all
> irrelevant for long term
> git logging and "git am" will take them off when Roland applies  the patch.
>
> Matan from Mellanox is reviewing the patch and will send ack or comments
> later today.
>
> The patch should be titled as follows
>
> IB/core:  An improved infrastructure for extending uverbs commands
>
> Or.
>

Really nice work. I also think it's better to move the comp_mask to the 
extended header in order to force future proof.
In addition, commands that have extensible sub-structures (for example, 
extended address handle in QP attributes in IP based addressing patch) 
should be given as a different UDATA in the cmd structure. Therefore, we 
need a comp_mask in the cmd structure header to describe which UDATA 
structure are included.

Regards,
Matan
--
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

  parent reply	other threads:[~2013-10-01 11:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 16:16 [PATCH] An improved infrastructure for uverbs commands (My take at designing extensible scheme) Yann Droneaud
     [not found] ` <1380039392-15480-1-git-send-email-ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
2013-10-01 10:58   ` Or Gerlitz
     [not found]     ` <524AAAE6.3040508-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-01 11:43       ` Matan Barak [this message]
     [not found]         ` <524AB54F.9050205-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-01 13:13           ` Yann Droneaud
     [not found]             ` <a8f6521f905732e511576cbc3768f254-zgzEX58YAwA@public.gmane.org>
2013-10-01 13:32               ` Matan Barak
     [not found]                 ` <524ACF03.3010302-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-01 13:53                   ` Yann Droneaud
     [not found]                     ` <7a32cf4322932c154e9bc145d8cf9ba0-zgzEX58YAwA@public.gmane.org>
2013-10-01 14:32                       ` Matan Barak
     [not found]                         ` <524ADCF1.80508-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-06  8:28                           ` Or Gerlitz
2013-10-01 12:54       ` Yann Droneaud

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=524AB54F.9050205@mellanox.com \
    --to=matanb-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=Igor.Ivanov-wN0M4riKYwLQT0dZR+AlfA@public.gmane.org \
    --cc=hadarh-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org \
    --cc=ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox