From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Stephen Bates <sbates@raithlin.com>,
Dan Williams <dan.j.williams@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
linux-rdma@vger.kernel.org, linux-block@vger.kernel.org,
Linux MM <linux-mm@kvack.org>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Matthew Wilcox <willy@linux.intel.com>,
jgunthorpe@obsidianresearch.com, haggaie@mellanox.com,
Christoph Hellwig <hch@infradead.org>, Jens Axboe <axboe@fb.com>,
Jonathan Corbet <corbet@lwn.net>,
jim.macdonald@everspin.com, sbates@raithin.com,
Logan Gunthorpe <logang@deltatee.com>,
David Woodhouse <dwmw2@infradead.org>,
"Raj, Ashok" <ashok.raj@intel.com>
Subject: Re: [PATCH 0/3] iopmem : A block device for PCIe memory
Date: Fri, 21 Oct 2016 02:57:14 -0700 [thread overview]
Message-ID: <20161021095714.GA12209@infradead.org> (raw)
In-Reply-To: <20161020232239.GQ23194@dastard>
On Fri, Oct 21, 2016 at 10:22:39AM +1100, Dave Chinner wrote:
> You do realise that local filesystems can silently change the
> location of file data at any point in time, so there is no such
> thing as a "stable mapping" of file data to block device addresses
> in userspace?
>
> If you want remote access to the blocks owned and controlled by a
> filesystem, then you need to use a filesystem with a remote locking
> mechanism to allow co-ordinated, coherent access to the data in
> those blocks. Anything else is just asking for ongoing, unfixable
> filesystem corruption or data leakage problems (i.e. security
> issues).
And at least for XFS we have such a mechanism :) E.g. I have a
prototype of a pNFS layout that uses XFS+DAX to allow clients to do
RDMA directly to XFS files, with the same locking mechanism we use
for the current block and scsi layout in xfs_pnfs.c.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
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>,
"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>, Christoph Hellwig <hch@infradead.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/3] iopmem : A block device for PCIe memory
Date: Fri, 21 Oct 2016 02:57:14 -0700 [thread overview]
Message-ID: <20161021095714.GA12209@infradead.org> (raw)
In-Reply-To: <20161020232239.GQ23194@dastard>
On Fri, Oct 21, 2016 at 10:22:39AM +1100, Dave Chinner wrote:
> You do realise that local filesystems can silently change the
> location of file data at any point in time, so there is no such
> thing as a "stable mapping" of file data to block device addresses
> in userspace?
>
> If you want remote access to the blocks owned and controlled by a
> filesystem, then you need to use a filesystem with a remote locking
> mechanism to allow co-ordinated, coherent access to the data in
> those blocks. Anything else is just asking for ongoing, unfixable
> filesystem corruption or data leakage problems (i.e. security
> issues).
And at least for XFS we have such a mechanism :) E.g. I have a
prototype of a pNFS layout that uses XFS+DAX to allow clients to do
RDMA directly to XFS files, with the same locking mechanism we use
for the current block and scsi layout in xfs_pnfs.c.
_______________________________________________
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@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Stephen Bates <sbates@raithlin.com>,
Dan Williams <dan.j.williams@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
linux-rdma@vger.kernel.org, linux-block@vger.kernel.org,
Linux MM <linux-mm@kvack.org>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Matthew Wilcox <willy@linux.intel.com>,
jgunthorpe@obsidianresearch.com, haggaie@mellanox.com,
Christoph Hellwig <hch@infradead.org>, Jens Axboe <axboe@fb.com>,
Jonathan Corbet <corbet@lwn.net>,
jim.macdonald@everspin.com, sbates@raithin.com,
Logan Gunthorpe <logang@deltatee.com>,
David Woodhouse <dwmw2@infradead.org>,
"Raj, Ashok" <ashok.raj@intel.com>
Subject: Re: [PATCH 0/3] iopmem : A block device for PCIe memory
Date: Fri, 21 Oct 2016 02:57:14 -0700 [thread overview]
Message-ID: <20161021095714.GA12209@infradead.org> (raw)
In-Reply-To: <20161020232239.GQ23194@dastard>
On Fri, Oct 21, 2016 at 10:22:39AM +1100, Dave Chinner wrote:
> You do realise that local filesystems can silently change the
> location of file data at any point in time, so there is no such
> thing as a "stable mapping" of file data to block device addresses
> in userspace?
>
> If you want remote access to the blocks owned and controlled by a
> filesystem, then you need to use a filesystem with a remote locking
> mechanism to allow co-ordinated, coherent access to the data in
> those blocks. Anything else is just asking for ongoing, unfixable
> filesystem corruption or data leakage problems (i.e. security
> issues).
And at least for XFS we have such a mechanism :) E.g. I have a
prototype of a pNFS layout that uses XFS+DAX to allow clients to do
RDMA directly to XFS files, with the same locking mechanism we use
for the current block and scsi layout in xfs_pnfs.c.
--
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-21 9:57 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 [this message]
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
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=20161021095714.GA12209@infradead.org \
--to=hch@infradead.org \
--cc=ashok.raj@intel.com \
--cc=axboe@fb.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--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=logang@deltatee.com \
--cc=ross.zwisler@linux.intel.com \
--cc=sbates@raithin.com \
--cc=sbates@raithlin.com \
--cc=willy@linux.intel.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.