> -----Original Message----- > From: Sagi Grimberg [mailto:sagig@xxxxxxxxxxxxxxxxxx] > Sent: Tuesday, June 30, 2015 4:33 AM > To: Steve Wise; dledford@xxxxxxxxxx > Cc: roid@xxxxxxxxxxxx; sagig@xxxxxxxxxxxx; linux-rdma@xxxxxxxxxxxxxxx; jgunthorpe@xxxxxxxxxxxxxxxxxxxx; infinipath@xxxxxxxxx; > eli@xxxxxxxxxxxx; ogerlitz@xxxxxxxxxxxx; sean.hefty@xxxxxxxxx; target-devel > Subject: Re: [PATCH V2 0/5] iSER support for iWARP > > On 6/30/2015 12:36 AM, Steve Wise wrote: > > The following series implements support for iWARP transports in the iSER > > initiator and target. This is based on Doug's k.o/for-4.2 branch. > > > > I've tested this on cxgb4 and mlx4 hardware. > > > > Changes since V1: > > > > Introduce and use transport-independent RDMA core services for allocating > > DMA MRs and computing fast register access flags. > > > > Correctly set the device max_sge_rd capability in several rdma device > > drivers. > > > > isert: use device capability max_sge_rd for the read sge depth. > > > > isert: change max_sge to max_write_sge in struct isert_conn. > > > > Steve, > > iser-target related code is usually posted/reviewed on the target-devel > mailing list and merged via target-pending tree. > > Please CC target-devel in future patches that involve iser-target. > > Thanks, > Sagi. Sorry, my bad. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html