On Tue, 2015-08-04 at 12:09 -0600, Jason Gunthorpe wrote: > On Mon, Aug 03, 2015 at 11:33:51AM -0700, Bart Van Assche wrote: > > >Bart, do you know what hardware this workaround is for? > > > > I hope the HW vendors can comment on this. Sorry but I'm not sure which HCA > > models and/or firmware versions do not support FMR mapping with a non-zero > > offset. > > Perhaps David can remember why he added this: > > commit 8f26c9ff9cd0317ad867bce972f69e0c6c2cbe3c
It's originally from commit 559ce8f150d7d031c79c4d79173860f1bdfe3ce4, and the list's attempts at code archaeology failed us: http://article.gmane.org/gmane.linux.drivers.rdma/7149 > The way it is phrased makes it seem like a target bug, not a HCA bug? Yes, the original commit is explicit about it being a target issue. Since it mentioned the boogeyman words "data corruption", I kept the work around in the FMR work. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
