From: Christoph Hellwig <hch@infradead.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Chinner <david@fromorbit.com>,
jgunthorpe@obsidianresearch.com, sbates@raithin.com, "Raj,
Ashok" <ashok.raj@intel.com>,
haggaie@mellanox.com, linux-rdma@vger.kernel.org,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jim.macdonald@everspin.com, Stephen Bates <sbates@raithlin.com>,
linux-block@vger.kernel.org, Linux MM <linux-mm@kvack.org>,
Jens Axboe <axboe@fb.com>, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/3] iopmem : A block device for PCIe memory
Date: Thu, 27 Oct 2016 05:32:19 -0700 [thread overview]
Message-ID: <20161027123219.GA757@infradead.org> (raw)
In-Reply-To: <76e957c9-8002-5a46-8111-269bb0401718@grimberg.me>
On Thu, Oct 27, 2016 at 01:22:49PM +0300, Sagi Grimberg wrote:
> Christoph, did you manage to leap to the future and solve the
> RDMA persistency hole? :)
>
> e.g. what happens with O_DSYNC in this model? Or you did
> a message exchange for commits?
Yes, pNFS calls this the layoutcommit. That being said once we get a RDMA
commit or flush operation we could easily make the layoutcommit optional
for some operations. There already is a precedence for the in the
flexfiles layout specification.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: jgunthorpe@obsidianresearch.com, sbates@raithin.com, "Raj,
Ashok <ashok.raj@intel.com>,
haggaie@mellanox.com, linux-rdma@vger.kernel.org,
linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
Jonathan Corbet <corbet@lwn.net>,
Dave Chinner <david@fromorbit.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jim.macdonald@everspin.com, Stephen Bates <sbates@raithlin.com>,
Christoph Hellwig <hch@infradead.org>,
Linux MM <linux-mm@kvack.org>,
linux-block@vger.kernel.org, Jens Axboe <axboe@fb.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/3] iopmem : A block device for PCIe memory
Date: Thu, 27 Oct 2016 05:32:19 -0700 [thread overview]
Message-ID: <20161027123219.GA757@infradead.org> (raw)
In-Reply-To: <76e957c9-8002-5a46-8111-269bb0401718@grimberg.me>
On Thu, Oct 27, 2016 at 01:22:49PM +0300, Sagi Grimberg wrote:
> Christoph, did you manage to leap to the future and solve the
> RDMA persistency hole? :)
>
> e.g. what happens with O_DSYNC in this model? Or you did
> a message exchange for commits?
Yes, pNFS calls this the layoutcommit. That being said once we get a RDMA
commit or flush operation we could easily make the layoutcommit optional
for some operations. There already is a precedence for the in the
flexfiles layout specification.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
Cc: jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org,
sbates-Rgftl6RXld5BDgjK7y7TUQ@public.gmane.org, "Raj,
Ashok" <ashok.raj-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
haggaie-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org"
<linux-nvdimm-y27Ovi1pjclAfugRpC6u6w@public.gmane.org>,
Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>,
Dave Chinner <david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
jim.macdonald-FgSLVYC75IpWk0Htik3J/w@public.gmane.org,
Stephen Bates <sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org>,
Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Linux MM <linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>,
linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Jens Axboe <axboe-b10kYP2dOMg@public.gmane.org>,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Subject: Re: [PATCH 0/3] iopmem : A block device for PCIe memory
Date: Thu, 27 Oct 2016 05:32:19 -0700 [thread overview]
Message-ID: <20161027123219.GA757@infradead.org> (raw)
In-Reply-To: <76e957c9-8002-5a46-8111-269bb0401718-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
On Thu, Oct 27, 2016 at 01:22:49PM +0300, Sagi Grimberg wrote:
> Christoph, did you manage to leap to the future and solve the
> RDMA persistency hole? :)
>
> e.g. what happens with O_DSYNC in this model? Or you did
> a message exchange for commits?
Yes, pNFS calls this the layoutcommit. That being said once we get a RDMA
commit or flush operation we could easily make the layoutcommit optional
for some operations. There already is a precedence for the in the
flexfiles layout specification.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Chinner <david@fromorbit.com>,
jgunthorpe@obsidianresearch.com, sbates@raithin.com, "Raj,
Ashok" <ashok.raj@intel.com>,
haggaie@mellanox.com, linux-rdma@vger.kernel.org,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jim.macdonald@everspin.com, Stephen Bates <sbates@raithlin.com>,
linux-block@vger.kernel.org, Linux MM <linux-mm@kvack.org>,
Jens Axboe <axboe@fb.com>, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/3] iopmem : A block device for PCIe memory
Date: Thu, 27 Oct 2016 05:32:19 -0700 [thread overview]
Message-ID: <20161027123219.GA757@infradead.org> (raw)
In-Reply-To: <76e957c9-8002-5a46-8111-269bb0401718@grimberg.me>
On Thu, Oct 27, 2016 at 01:22:49PM +0300, Sagi Grimberg wrote:
> Christoph, did you manage to leap to the future and solve the
> RDMA persistency hole? :)
>
> e.g. what happens with O_DSYNC in this model? Or you did
> a message exchange for commits?
Yes, pNFS calls this the layoutcommit. That being said once we get a RDMA
commit or flush operation we could easily make the layoutcommit optional
for some operations. There already is a precedence for the in the
flexfiles layout specification.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-10-27 13:50 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 21:42 [PATCH 0/3] iopmem : A block device for PCIe memory Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-18 21:42 ` [PATCH 1/3] memremap.c : Add support for ZONE_DEVICE IO memory with struct pages Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-19 17:50 ` Dan Williams
2016-10-19 17:50 ` Dan Williams
2016-10-19 17:50 ` Dan Williams
2016-10-19 17:50 ` Dan Williams
2016-10-19 17:50 ` Dan Williams
2016-10-19 18:40 ` Stephen Bates
2016-10-19 18:40 ` Stephen Bates
2016-10-19 18:40 ` Stephen Bates
2016-10-19 20:01 ` Dan Williams
2016-10-19 20:01 ` Dan Williams
2016-10-19 20:01 ` Dan Williams
2016-10-19 20:01 ` Dan Williams
2016-10-19 20:01 ` Dan Williams
2016-10-25 11:54 ` Stephen Bates
2016-10-25 11:54 ` Stephen Bates
2016-10-25 11:54 ` Stephen Bates
2016-10-25 11:54 ` Stephen Bates
2016-10-18 21:42 ` [PATCH 2/3] iopmem : Add a block device driver for PCIe attached IO memory Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-28 6:45 ` Christoph Hellwig
2016-10-28 6:45 ` Christoph Hellwig
2016-10-28 6:45 ` Christoph Hellwig
2016-10-28 19:22 ` Logan Gunthorpe
2016-10-28 19:22 ` Logan Gunthorpe
2016-10-28 19:22 ` Logan Gunthorpe
2016-10-18 21:42 ` [PATCH 3/3] iopmem : Add documentation for iopmem driver Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-18 21:42 ` Stephen Bates
2016-10-28 6:46 ` Christoph Hellwig
2016-10-28 6:46 ` Christoph Hellwig
2016-10-28 6:46 ` Christoph Hellwig
2016-10-19 3:51 ` [PATCH 0/3] iopmem : A block device for PCIe memory Dan Williams
2016-10-19 3:51 ` Dan Williams
2016-10-19 3:51 ` Dan Williams
2016-10-19 3:51 ` Dan Williams
2016-10-19 18:48 ` Stephen Bates
2016-10-19 18:48 ` Stephen Bates
2016-10-19 18:48 ` Stephen Bates
2016-10-19 18:48 ` Stephen Bates
2016-10-19 19:58 ` Dan Williams
2016-10-19 19:58 ` Dan Williams
2016-10-19 19:58 ` Dan Williams
2016-10-19 19:58 ` Dan Williams
2016-10-19 22:54 ` Stephen Bates
2016-10-19 22:54 ` Stephen Bates
2016-10-19 22:54 ` Stephen Bates
2016-10-19 22:54 ` Stephen Bates
2016-10-20 23:22 ` Dave Chinner
2016-10-20 23:22 ` Dave Chinner
2016-10-20 23:22 ` Dave Chinner
2016-10-20 23:22 ` Dave Chinner
2016-10-21 9:57 ` Christoph Hellwig
2016-10-21 9:57 ` Christoph Hellwig
2016-10-21 9:57 ` Christoph Hellwig
2016-10-21 11:12 ` Dave Chinner
2016-10-21 11:12 ` Dave Chinner
2016-10-21 11:12 ` Dave Chinner
2016-10-25 11:50 ` Stephen Bates
2016-10-25 11:50 ` Stephen Bates
2016-10-25 11:50 ` Stephen Bates
2016-10-25 21:19 ` Dave Chinner
2016-10-25 21:19 ` Dave Chinner
2016-10-25 21:19 ` Dave Chinner
2016-11-06 14:05 ` Stephen Bates
2016-11-06 14:05 ` Stephen Bates
2016-11-06 14:05 ` Stephen Bates
2016-11-06 14:05 ` Stephen Bates
2016-10-27 10:22 ` Sagi Grimberg
2016-10-27 10:22 ` Sagi Grimberg
2016-10-27 10:22 ` Sagi Grimberg
2016-10-27 12:32 ` Christoph Hellwig [this message]
2016-10-27 12:32 ` Christoph Hellwig
2016-10-27 12:32 ` Christoph Hellwig
2016-10-27 12:32 ` Christoph Hellwig
2016-10-26 8:24 ` Haggai Eran
2016-10-26 8:24 ` Haggai Eran
2016-10-26 8:24 ` Haggai Eran
2016-10-26 8:24 ` Haggai Eran
2016-10-26 8:24 ` Haggai Eran
2016-10-26 13:39 ` Dan Williams
2016-10-26 13:39 ` Dan Williams
2016-10-26 13:39 ` Dan Williams
2016-10-26 13:39 ` Dan Williams
2016-10-26 13:39 ` Dan Williams
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=20161027123219.GA757@infradead.org \
--to=hch@infradead.org \
--cc=ashok.raj@intel.com \
--cc=axboe@fb.com \
--cc=corbet@lwn.net \
--cc=david@fromorbit.com \
--cc=dwmw2@infradead.org \
--cc=haggaie@mellanox.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=jim.macdonald@everspin.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=sbates@raithin.com \
--cc=sbates@raithlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.