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:39:18 +0200 Message-ID: <5641E576.7010503@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> <5641E2D1.8070209@dev.mellanox.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5641E2D1.8070209-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Sagi Grimberg , Yann Droneaud Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-rdma@vger.kernel.org On 10/11/2015 14:28, Sagi Grimberg wrote: > Hi Yann, > >> >> Why were those hw providers not modified to >> enforce IB_ACCESS_REMOTE_WRITE when needed, instead of asking users to >> set it for them ? > > Do you mean that ULPs will set IB_ACCESS_LOCAL_WRITE and > iWARP providers executing the memory registration will add > IB_ACCESS_REMOTE_WRITE? That's even better I think! Given that > changing the access rights under the user legs is something we'd want > to do. is it? Oh, forgot that the providers do not know how this key will be used. Thanks Tom for reminding me. -- 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