public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	"Hefty,
	Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Roland Dreier <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Oren Duer <oren-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	tzahio-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH RFC v1 00/10] Introduce Signature feature
Date: Thu, 31 Oct 2013 11:29:54 +0200	[thread overview]
Message-ID: <52722312.3040907@mellanox.com> (raw)
In-Reply-To: <52712BE4.3060103-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

On 10/30/2013 5:55 PM, Or Gerlitz wrote:
> On 30/10/2013 17:20, Hefty, Sean wrote:
>>> The team here enhanced krping to fully cover (and test...) the proposed
>>> >API and driver implementation, its (free) under
>>> >git://beany.openfabrics.org/~sgrimberg/krping.git
>>> >
>>> >We'd like to see this landing in 3.13 such that the development of the
>>> >upper layers can run for 3.14 and and later kernels. Sagi will postV2
>>> >with the two minor changes that came up in Sean's review of V1, 
>>> thoughts?
>> If the upper layers won't be ready until 3.14, why can't these 
>> changes go in then?
>
> I explained, we want to see this landing in sooner rather than later 
> to avoid triple/quadruple way merge, e.g merge
> of code from multiple kernel sub-components in one kernel cycle which 
> is complex.
>
>> My biggest issue is that the kernel verbs API is becoming more and 
>> more unwieldy, and I have heard requests that even the kernel 
>> interfaces need to be easier to use.  The main work request structure 
>> used to send a message is around 84 bytes long.  This patch bumps 
>> that up another 24 bytes or so.  That's over 100 bytes of control 
>> data just to send a message!
>>

Hey Sean,
You are raising a good point, I noticed that too.
I can modify the sig_handover wr extension not to increase structure size.
I'll use ib_sges instead of {mr, va, len}. data ib_sge will be passed in 
the existing wr->sg_list, and the protection ib_sge will be passed in 
sig_handover extension.

I'll fix & send v2 today.

>> Maybe we should rethink the approach of exposing low-level hardware 
>> constructs to every distinct feature of every vendor's latest 
>> hardware directly to the kernel ULPs.
>
> T10 DIF is industry standard, and it used in advanced commercial 
> production storage systems, the feature here is T10 DIF acceleration 
> for layers (e.g iser/srp/fcoe initiator/targets) that use RDMA. This 
> feature is supported by some FC cards too, so we want RDMA to be 
> competitive. We made great effort to expose API which is not tied to 
> specific HW/Firmware API.
>
> 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-31  9:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 14:26 [PATCH RFC v1 00/10] Introduce Signature feature Sagi Grimberg
     [not found] ` <1382970376-13776-1-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-28 14:26   ` [PATCH RFC v1 01/10] IB/core: Introduce protected memory regions Sagi Grimberg
     [not found]     ` <1382970376-13776-2-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-28 21:22       ` Hefty, Sean
     [not found]         ` <1828884A29C6694DAF28B7E6B8A8237388CF1CDD-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-10-29  7:25           ` Or Gerlitz
     [not found]             ` <526F62DA.4050304-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-29 19:34               ` Hefty, Sean
     [not found]                 ` <1828884A29C6694DAF28B7E6B8A8237388CF25C5-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-10-29 20:20                   ` Or Gerlitz
2013-10-29  8:15           ` Sagi Grimberg
2013-10-28 14:26   ` [PATCH RFC v1 02/10] IB/core: Introduce Signature Verbs API Sagi Grimberg
2013-10-28 14:26   ` [PATCH RFC v1 03/10] IB/mlx5, mlx5_core: Support for create_mr and destroy_mr Sagi Grimberg
2013-10-28 14:26   ` [PATCH RFC v1 04/10] IB/mlx5: Initialize mlx5_ib_qp signature related Sagi Grimberg
2013-10-28 14:26   ` [PATCH RFC v1 05/10] IB/mlx5: Break wqe handling to begin & finish routines Sagi Grimberg
2013-10-28 14:26   ` [PATCH RFC v1 06/10] IB/mlx5: remove MTT access mode from umr flags helper function Sagi Grimberg
2013-10-28 14:26   ` [PATCH RFC v1 07/10] IB/mlx5: Keep mlx5 MRs in a radix tree under device Sagi Grimberg
2013-10-28 14:26   ` [PATCH RFC v1 08/10] IB/mlx5: Support IB_WR_REG_SIG_MR Sagi Grimberg
2013-10-28 14:26   ` [PATCH RFC v1 09/10] IB/mlx5: Collect signature error completion Sagi Grimberg
2013-10-28 14:26   ` [PATCH RFC v1 10/10] IB/mlx5: Publish support in signature feature Sagi Grimberg
2013-10-30 10:29   ` [PATCH RFC v1 00/10] Introduce Signature feature Or Gerlitz
     [not found]     ` <5270DF90.8000802-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-30 15:20       ` Hefty, Sean
     [not found]         ` <1828884A29C6694DAF28B7E6B8A8237388CF28A5-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-10-30 15:55           ` Or Gerlitz
     [not found]             ` <52712BE4.3060103-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-31  9:29               ` Sagi Grimberg [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=52722312.3040907@mellanox.com \
    --to=sagig-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=oren-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=tzahio-VPRAkNaXOzVWk0Htik3J/w@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