diff for duplicates of <20190627170027.GE10652@lst.de> diff --git a/a/1.txt b/N1/1.txt index b56c149..dce662d 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -On Thu, Jun 27, 2019 at 10:30:42AM -0600, Logan Gunthorpe wrote: +On Thu, Jun 27, 2019@10:30:42AM -0600, Logan Gunthorpe wrote: > > (a) a range is normal RAM, DMA mapping works as usual > > (b) a range is another devices BAR, in which case we need to do a > > map_resource equivalent (which really just means don't bother with @@ -47,7 +47,7 @@ chain of problems. > three types doesn't seem useful. bio_vec flags also make it easy to > support mixing segments from different memory types. -So I іnitially suggested these flags. But without a pgmap we absolutely +So I ?nitially suggested these flags. But without a pgmap we absolutely need a lookup operation to find which phys address ranges map to which device. And once we do that the data structure the only thing we need is a flag saying that we need that information, and everything else diff --git a/a/content_digest b/N1/content_digest index 62197f9..5ce4689 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,26 +8,12 @@ "ref\08a0a08c3-a537-bff6-0852-a5f337a70688@deltatee.com\0" "ref\020190627090843.GB11548@lst.de\0" "ref\089889319-e778-7772-ab36-dc55b59826be@deltatee.com\0" - "From\0Christoph Hellwig <hch@lst.de>\0" - "Subject\0Re: [RFC PATCH 00/28] Removing struct page from P2PDMA\0" + "From\0hch@lst.de (Christoph Hellwig)\0" + "Subject\0[RFC PATCH 00/28] Removing struct page from P2PDMA\0" "Date\0Thu, 27 Jun 2019 19:00:27 +0200\0" - "To\0Logan Gunthorpe <logang@deltatee.com>\0" - "Cc\0Christoph Hellwig <hch@lst.de>" - Jason Gunthorpe <jgg@ziepe.ca> - linux-kernel@vger.kernel.org - linux-block@vger.kernel.org - linux-nvme@lists.infradead.org - linux-pci@vger.kernel.org - linux-rdma@vger.kernel.org - Jens Axboe <axboe@kernel.dk> - Bjorn Helgaas <bhelgaas@google.com> - Dan Williams <dan.j.williams@intel.com> - Sagi Grimberg <sagi@grimberg.me> - Keith Busch <kbusch@kernel.org> - " Stephen Bates <sbates@raithlin.com>\0" "\00:1\0" "b\0" - "On Thu, Jun 27, 2019 at 10:30:42AM -0600, Logan Gunthorpe wrote:\n" + "On Thu, Jun 27, 2019@10:30:42AM -0600, Logan Gunthorpe wrote:\n" "> > (a) a range is normal RAM, DMA mapping works as usual\n" "> > (b) a range is another devices BAR, in which case we need to do a\n" "> > map_resource equivalent (which really just means don't bother with\n" @@ -76,10 +62,10 @@ "> three types doesn't seem useful. bio_vec flags also make it easy to\n" "> support mixing segments from different memory types.\n" "\n" - "So I \321\226nitially suggested these flags. But without a pgmap we absolutely\n" + "So I ?nitially suggested these flags. But without a pgmap we absolutely\n" "need a lookup operation to find which phys address ranges map to which\n" "device. And once we do that the data structure the only thing we need\n" "is a flag saying that we need that information, and everything else\n" can be in the data structure returned from that lookup. -0217df9bf62ccb83fb4f39ed2b8c60d9d82c3c9c4937813c726bf95ce67cd958 +7dbd5941ea11faf0252425c1f2c7f0db580d67883d9887975f86684ac9904abd
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.