From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: Steve Wise <swise@opengridcomputing.com>, dledford@redhat.com
Cc: infinipath@intel.com, sagig@mellanox.com, ogerlitz@mellanox.com,
roid@mellanox.com, linux-rdma@vger.kernel.org, eli@mellanox.com,
target-devel@vger.kernel.org, linux-nfs@vger.kernel.org,
bfields@fieldses.org
Subject: Re: [PATCH V6 6/9] isert: Rename IO functions to more descriptive names
Date: Thu, 6 Aug 2015 18:37:39 +0300 [thread overview]
Message-ID: <55C37F43.6080106@dev.mellanox.co.il> (raw)
In-Reply-To: <00b001d0cfc4$f83a14c0$e8ae3e40$@opengridcomputing.com>
On 8/6/2015 12:23 AM, Steve Wise wrote:
>
>>>
>>>> Hey Sagi, how is this coming along? How can I help?
>>>>
>>>
>>> Hi Steve,
>>>
>>> This is taking longer than I expected, the changes needed seem
>>> pretty extensive throughout the IO path. I don't think it will be ready
>>> for 4.3
>>>
>>
>> Perhaps then we should go with my version that adds iwarp-only FRMR IO handlers for 4.3. Then they can be phased out as the rework
>> matures. Thoughts?
>>
>
> Shall I send out the series again for merging into 4.3?
Hi Steve,
Not sure about that.. I'm a bit reluctant in adding a code that
branches the isert code even more than it already is.
Nic, WDYT?
WARNING: multiple messages have this Message-ID (diff)
From: Sagi Grimberg <sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Steve Wise
<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: infinipath-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
roid-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
target-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org
Subject: Re: [PATCH V6 6/9] isert: Rename IO functions to more descriptive names
Date: Thu, 6 Aug 2015 18:37:39 +0300 [thread overview]
Message-ID: <55C37F43.6080106@dev.mellanox.co.il> (raw)
In-Reply-To: <00b001d0cfc4$f83a14c0$e8ae3e40$@opengridcomputing.com>
On 8/6/2015 12:23 AM, Steve Wise wrote:
>
>>>
>>>> Hey Sagi, how is this coming along? How can I help?
>>>>
>>>
>>> Hi Steve,
>>>
>>> This is taking longer than I expected, the changes needed seem
>>> pretty extensive throughout the IO path. I don't think it will be ready
>>> for 4.3
>>>
>>
>> Perhaps then we should go with my version that adds iwarp-only FRMR IO handlers for 4.3. Then they can be phased out as the rework
>> matures. Thoughts?
>>
>
> Shall I send out the series again for merging into 4.3?
Hi Steve,
Not sure about that.. I'm a bit reluctant in adding a code that
branches the isert code even more than it already is.
Nic, WDYT?
--
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
next prev parent reply other threads:[~2015-08-06 15:37 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 16:18 [PATCH V6 0/9] iSER support for iWARP Steve Wise
2015-07-24 16:18 ` Steve Wise
2015-07-24 16:18 ` [PATCH V6 1/9] RDMA/iser: Limit sg tablesize and max_sectors to device fastreg max depth Steve Wise
2015-07-24 16:18 ` Steve Wise
2015-07-24 16:41 ` Jason Gunthorpe
2015-07-24 16:41 ` Jason Gunthorpe
2015-07-24 18:40 ` Steve Wise
2015-07-24 18:40 ` Steve Wise
2015-07-24 19:14 ` Jason Gunthorpe
2015-07-26 9:58 ` Sagi Grimberg
2015-07-26 9:57 ` Sagi Grimberg
2015-07-26 9:57 ` Sagi Grimberg
2015-07-24 16:18 ` [PATCH V6 2/9] mlx4, mlx5, mthca: Expose max_sge_rd correctly Steve Wise
2015-07-24 16:18 ` Steve Wise
2015-07-24 16:18 ` [PATCH V6 3/9] ipath,qib: " Steve Wise
2015-07-24 16:18 ` Steve Wise
2015-07-24 16:18 ` [PATCH V6 4/9] svcrdma: Use max_sge_rd for destination read depths Steve Wise
2015-07-24 16:18 ` Steve Wise
2015-07-24 18:51 ` Steve Wise
2015-07-24 18:51 ` Steve Wise
2015-07-26 9:58 ` Sagi Grimberg
2015-07-26 10:42 ` Christoph Hellwig
2015-07-26 10:42 ` Christoph Hellwig
2015-07-24 16:18 ` [PATCH V6 5/9] RDMA/isert: Limit read depth based on the device max_sge_rd capability Steve Wise
2015-07-24 16:18 ` [PATCH V6 6/9] isert: Rename IO functions to more descriptive names Steve Wise
2015-07-24 16:18 ` Steve Wise
2015-07-26 10:08 ` Sagi Grimberg
2015-07-26 10:08 ` Sagi Grimberg
2015-07-26 10:43 ` Christoph Hellwig
2015-07-26 10:43 ` Christoph Hellwig
2015-07-26 11:00 ` Sagi Grimberg
2015-07-26 11:00 ` Sagi Grimberg
2015-07-26 15:53 ` Christoph Hellwig
2015-07-26 16:44 ` Sagi Grimberg
2015-07-26 17:32 ` Steve Wise
2015-07-26 17:32 ` Steve Wise
2015-07-26 17:40 ` Sagi Grimberg
2015-07-26 20:15 ` Steve Wise
2015-07-26 20:15 ` Steve Wise
2015-07-26 20:17 ` Steve Wise
2015-07-26 20:17 ` Steve Wise
2015-07-27 21:45 ` Steve Wise
2015-07-27 21:45 ` Steve Wise
2015-08-03 19:32 ` Steve Wise
2015-08-03 19:32 ` Steve Wise
2015-08-04 17:26 ` Sagi Grimberg
2015-08-04 17:44 ` Steve Wise
2015-08-04 17:44 ` Steve Wise
2015-08-05 21:23 ` Steve Wise
2015-08-05 21:23 ` Steve Wise
2015-08-06 15:37 ` Sagi Grimberg [this message]
2015-08-06 15:37 ` Sagi Grimberg
2015-08-12 22:15 ` Steve Wise
2015-08-12 22:15 ` Steve Wise
2015-08-13 13:09 ` Sagi Grimberg
2015-07-24 16:18 ` [PATCH V6 7/9] isert: Use the device's max fastreg page list depth Steve Wise
2015-07-24 16:18 ` [PATCH V6 8/9] isert: Use local_dma_lkey whenever possible Steve Wise
2015-07-24 16:49 ` Jason Gunthorpe
2015-07-24 16:49 ` Jason Gunthorpe
2015-07-24 18:41 ` Steve Wise
2015-07-24 18:41 ` Steve Wise
2015-07-24 16:19 ` [PATCH V6 9/9] isert: Support iWARP transports using FRMRs Steve Wise
2015-07-24 16:57 ` Jason Gunthorpe
2015-07-24 18:48 ` Steve Wise
2015-07-24 18:48 ` Steve Wise
2015-07-24 19:24 ` Jason Gunthorpe
2015-07-24 19:24 ` Jason Gunthorpe
2015-07-24 19:57 ` Steve Wise
2015-07-24 19:57 ` Steve Wise
2015-07-24 22:11 ` Steve Wise
2015-07-24 22:11 ` Steve Wise
2015-07-24 22:38 ` Jason Gunthorpe
2015-07-24 22:38 ` Jason Gunthorpe
2015-07-26 10:23 ` Sagi Grimberg
2015-07-26 10:23 ` Sagi Grimberg
2015-07-27 17:07 ` Jason Gunthorpe
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=55C37F43.6080106@dev.mellanox.co.il \
--to=sagig@dev.mellanox.co.il \
--cc=bfields@fieldses.org \
--cc=dledford@redhat.com \
--cc=eli@mellanox.com \
--cc=infinipath@intel.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=roid@mellanox.com \
--cc=sagig@mellanox.com \
--cc=swise@opengridcomputing.com \
--cc=target-devel@vger.kernel.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.