From: "Michael S. Tsirkin" <mst@redhat.com>
To: Roland Dreier <roland@kernel.org>
Cc: qemu-devel@nongnu.org,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Yishai Hadas <yishaih@mellanox.com>,
LKML <linux-kernel@vger.kernel.org>,
"Michael R. Hines" <mrhines@linux.vnet.ibm.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
Sean Hefty <sean.hefty@intel.com>,
Christoph Lameter <cl@linux.com>
Subject: Re: [Qemu-devel] [PATCH] rdma: don't make pages writeable if not requiested
Date: Thu, 21 Mar 2013 11:39:47 +0200 [thread overview]
Message-ID: <20130321093946.GG28328@redhat.com> (raw)
In-Reply-To: <CAL1RGDVnkLZU2Vge4o3BwDxnAfGv7TQRMqE6ha3MUt39CVp5NQ@mail.gmail.com>
On Thu, Mar 21, 2013 at 02:13:38AM -0700, Roland Dreier wrote:
> On Thu, Mar 21, 2013 at 1:51 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
> >> In that case, no, I don't see any reason for LOCAL_WRITE, since the
> >> only RDMA operations that will access this memory are remote reads.
> >
> > What is the meaning of LOCAL_WRITE then? There are no local
> > RDMA writes as far as I can see.
>
> Umm, it means you're giving the local adapter permission to write to
> that memory. So you can use it as a receive buffer or as the target
> for remote data from an RDMA read operation.
Well RDMA read has it's own flag, IB_ACCESS_REMOTE_READ.
I don't see why do you need to give adapter permission
to use memory as a receive buffer given that
you must pass the address in the post receive verb,
but maybe that's what the IB spec says so that's what
the applications assumed?
> > OK then what we need is a new flag saying "I really do not
> > intend to write into this memory please do not break
> > COW or do anything else just in case I do".
>
> Isn't that a shared read-only mapping?
>
> - R.
Nothing to do with how the page is mapped. We can and do write the page
before registration. BTW umem.c passes in force so it breaks COW
even for read-only mappings, right?
--
MST
next prev parent reply other threads:[~2013-03-21 9:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 6:18 [Qemu-devel] [PATCH] rdma: don't make pages writeable if not requiested Michael S. Tsirkin
2013-03-21 6:55 ` Roland Dreier
2013-03-21 7:03 ` Michael S. Tsirkin
2013-03-21 7:15 ` Roland Dreier
2013-03-21 8:51 ` Michael S. Tsirkin
2013-03-21 9:13 ` Roland Dreier
2013-03-21 9:39 ` Michael S. Tsirkin [this message]
2013-03-21 17:11 ` Jason Gunthorpe
2013-03-21 17:15 ` Michael S. Tsirkin
2013-03-21 17:21 ` Jason Gunthorpe
2013-03-21 17:42 ` Michael S. Tsirkin
2013-03-21 17:57 ` Jason Gunthorpe
2013-03-21 18:03 ` Michael S. Tsirkin
2013-03-21 18:16 ` Michael S. Tsirkin
2013-03-21 18:41 ` Jason Gunthorpe
2013-03-21 19:15 ` Michael S. Tsirkin
2013-03-21 20:09 ` Jason Gunthorpe
2013-03-21 9:32 ` Michael S. Tsirkin
2013-03-21 11:30 ` Michael S. Tsirkin
2013-03-21 12:23 ` Michael R. Hines
2013-03-21 12:32 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130321093946.GG28328@redhat.com \
--to=mst@redhat.com \
--cc=cl@linux.com \
--cc=hal.rosenstock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mrhines@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.com \
--cc=yishaih@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).