On 06/30/2015 02:42 PM, Steve Wise wrote:
> 
> 
>> -----Original Message-----
>> From: Hefty, Sean [mailto:sean.he...@intel.com]
>> Sent: Tuesday, June 30, 2015 12:04 PM
>> To: Jason Gunthorpe; Steve Wise
>> Cc: 'Sagi Grimberg'; dledf...@redhat.com; r...@mellanox.com; 
>> sa...@mellanox.com; linux-rdma@vger.kernel.org; infinipath;
>> e...@mellanox.com; ogerl...@mellanox.com
>> Subject: RE: [PATCH V2 4/5] RDMA/iser: support iWARP devices
>>
>>>> I prefer to decouple the iSER changes with this core work.
>>>> Jason/Sean... thoughts?  I could do the iSER w/o patch 3, and the
>>>> follow up with a series that includes our final solution on
>>>> transport independent memory registration and change all the TI
>>>> kernel users (iser and nfsrdma) along with it.
>>>
>>> There has a been a big push lately to drop the strange transport
>>> specific stuff - if you are comitted to seeing the access flag clean
>>> up series through then I don't see a problem with using whatever order
>>> you like.
>>
>> I agree.
> 
> Ok, then I'll do this:
> 
> 1) series with iser changes to enable iwarp including mlx/ipath/qib patches 
> to set max_sge_rd
> 2) series on transport independent access flags / memory reg - updating the 
> kernel ULPs too.

I've quickly reviewed the series and you plan here seems fine.  I'm
bouncing this out of my queue and will wait for the next version.

-- 
Doug Ledford <dledf...@redhat.com>
              GPG KeyID: 0E572FDD


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to