From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sagi Grimberg Subject: Re: [PATCH RFC 1/3] IB/core: Expose a device attribute for rdma_read access flags Date: Tue, 10 Nov 2015 14:42:44 +0200 Message-ID: <5641E644.7080101@mellanox.com> References: <1447152255-28231-1-git-send-email-sagig@mellanox.com> <1447152255-28231-2-git-send-email-sagig@mellanox.com> <1447156270.7089.3.camel@opteya.com> <5641E4C9.7000206@talpey.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5641E4C9.7000206-CLs1Zie5N5HQT0dZR+AlfA@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Tom Talpey , Yann Droneaud Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-rdma@vger.kernel.org > Sagi, the Windows NDKPI has an NDK_MR_FLAG_RDMA_READ_SINK attribute > which the upper layer can use to convey this information, I've mentioned > it here before. > https://msdn.microsoft.com/en-us/library/windows/hardware/hh439908(v=vs.85).aspx > Thanks for the tip Tom. > > When this approach is used, the upper layer doesn't have to be aware > at all of the lower layer's details. Yea, we could do that too. Any preferences from other people? I'm pretty indifferent on which way to go... Sagi. -- 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