All of lore.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Matan Barak <matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Yann Droneaud <ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>,
	Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>
Cc: 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 v2 4/4] IB/core: extended command: add a common extended response header
Date: Wed, 9 Oct 2013 13:30:40 +0300	[thread overview]
Message-ID: <52553050.8050501@mellanox.com> (raw)
In-Reply-To: <5253F37C.90508-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

On 08/10/2013 14:58, Matan Barak wrote:
> Regarding the last patch, you are right that it simplifies things for 
> creating new uverbs where command parts are in-lined one after 
> another, but the infrastructure got a bit more complex.
>
> If we're going to this direction, I think the we should also deal with 
> the problem of extending one of the command parts. Currently, we'll 
> have to put a comp_mask in the in-lined command part, consume this 
> command part and then continue with the other parts. It might be 
> better than using a pointer, but this put the burden of serializing 
> the command buffer into the kernel structures onto the uverb command 
> writer. We might want to avoid this.
>
> Furthermore, the comp_mask of the command is different than the 
> comp_mask of the response. Therefore, I don't think we should pass the 
> command's comp_mask to the uverb as a pointer, but just pass a pointer 
> to value 0 that the uverb will set. 

Guys, sounds to me it's a bit too late for patch #4 -- we have to leave 
something for the next generation to work on... we're after rc4 and we 
don't want to let 3.12 have different uverbs API vs future kernel just 
for the sake of fixing the issues Yan pointed on. I suggest that patches 
1-3 will go into 3.12 - Roland, are you willing to pick this up? We have 
Matan's ack.

Or.
--
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-09 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07 20:49 [PATCH v2 0/4] IB/core: an improved infrastructure for uverbs commands Yann Droneaud
     [not found] ` <cover.1381177342.git.ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
2013-10-07 20:49   ` [PATCH v2 1/4] IB/core: extended command: " Yann Droneaud
     [not found]     ` <70486466a70aae3e3facf5a12c1d0bb960a9a462.1381177342.git.ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
2013-10-09 11:38       ` Or Gerlitz
     [not found]         ` <5255402F.4000806-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-09 12:42           ` Yann Droneaud
2013-10-07 20:49   ` [PATCH v2 2/4] IB/core: extended command: move comp_mask to the extended header Yann Droneaud
2013-10-07 20:49   ` [PATCH v2 3/4] IB/core: extended command: enforce command size Yann Droneaud
2013-10-07 20:49   ` [PATCH v2 4/4] IB/core: extended command: add a common extended response header Yann Droneaud
     [not found]     ` <9e111d8215c1fd86b75db17f2c890f0f28e0d076.1381177342.git.ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
2013-10-08 11:58       ` Matan Barak
     [not found]         ` <5253F37C.90508-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-09 10:30           ` Or Gerlitz [this message]
     [not found]             ` <52553050.8050501-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-09 11:29               ` Yann Droneaud
     [not found]                 ` <0d695256ac989e7b1bcccd3a2bfafcbf-zgzEX58YAwA@public.gmane.org>
2013-10-09 11:33                   ` Or Gerlitz

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=52553050.8050501@mellanox.com \
    --to=ogerlitz-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=matanb-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 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.