diff for duplicates of <9020459.Ga31IGQ4TP@wuerfel> diff --git a/a/1.txt b/N1/1.txt index 5598285..897eccc 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ On Tuesday, January 10, 2017 3:48:39 PM CET Christoph Hellwig wrote: -> On Tue, Jan 10, 2017@12:01:05PM +0100, Arnd Bergmann wrote: +> On Tue, Jan 10, 2017 at 12:01:05PM +0100, Arnd Bergmann wrote: > > Another workaround me might need is to limit amount of concurrent DMA > > in the NVMe driver based on some platform quirk. The way that NVMe works, > > it can have very large amounts of data that is concurrently mapped into @@ -27,3 +27,8 @@ very limited with their coherent allocations. Good idea. Arnd + +_______________________________________________ +linux-arm-kernel mailing list +linux-arm-kernel@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-arm-kernel diff --git a/a/content_digest b/N1/content_digest index 07574a8..0a1843e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,13 +1,28 @@ "ref\01483044304-2085-1-git-send-email-nikita.yoush@cogentembedded.com\0" "ref\04137257.d2v87kqLLv@wuerfel\0" "ref\020170110144839.GB27156@lst.de\0" - "From\0arnd@linaro.org (Arnd Bergmann)\0" - "Subject\0NVMe vs DMA addressing limitations\0" + "From\0Arnd Bergmann <arnd@linaro.org>\0" + "Subject\0Re: NVMe vs DMA addressing limitations\0" "Date\0Tue, 10 Jan 2017 16:02:28 +0100\0" + "To\0linux-arm-kernel@lists.infradead.org\0" + "Cc\0Nikita Yushchenko <nikita.yoush@cogentembedded.com>" + Jens Axboe <axboe@fb.com> + Sagi Grimberg <sagi@grimberg.me> + linux-pci@vger.kernel.org + Catalin Marinas <catalin.marinas@arm.com> + Will Deacon <will.deacon@arm.com> + linux-kernel@vger.kernel.org + linux-nvme@lists.infradead.org + Keith Busch <keith.busch@intel.com> + Simon Horman <horms@verge.net.au> + linux-renesas-soc@vger.kernel.org + Bjorn Helgaas <bhelgaas@google.com> + artemi.ivanov@cogentembedded.com + " Christoph Hellwig <hch@lst.de>\0" "\00:1\0" "b\0" "On Tuesday, January 10, 2017 3:48:39 PM CET Christoph Hellwig wrote:\n" - "> On Tue, Jan 10, 2017@12:01:05PM +0100, Arnd Bergmann wrote:\n" + "> On Tue, Jan 10, 2017 at 12:01:05PM +0100, Arnd Bergmann wrote:\n" "> > Another workaround me might need is to limit amount of concurrent DMA\n" "> > in the NVMe driver based on some platform quirk. The way that NVMe works,\n" "> > it can have very large amounts of data that is concurrently mapped into\n" @@ -34,6 +49,11 @@ "\n" "Good idea.\n" "\n" - "\tArnd" + "\tArnd\n" + "\n" + "_______________________________________________\n" + "linux-arm-kernel mailing list\n" + "linux-arm-kernel@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -833f6592331454b3fcbd44b2c7e0ad8e30e5699c21a83587cab5b52f3e64d301 +ea20616a89c51a4aa221d52a81c4f28bb78571c1fc7328192fcf74d075940fe2
diff --git a/a/1.txt b/N2/1.txt index 5598285..cffd1ea 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,5 +1,5 @@ On Tuesday, January 10, 2017 3:48:39 PM CET Christoph Hellwig wrote: -> On Tue, Jan 10, 2017@12:01:05PM +0100, Arnd Bergmann wrote: +> On Tue, Jan 10, 2017 at 12:01:05PM +0100, Arnd Bergmann wrote: > > Another workaround me might need is to limit amount of concurrent DMA > > in the NVMe driver based on some platform quirk. The way that NVMe works, > > it can have very large amounts of data that is concurrently mapped into diff --git a/a/content_digest b/N2/content_digest index 07574a8..94968ed 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,13 +1,28 @@ "ref\01483044304-2085-1-git-send-email-nikita.yoush@cogentembedded.com\0" "ref\04137257.d2v87kqLLv@wuerfel\0" "ref\020170110144839.GB27156@lst.de\0" - "From\0arnd@linaro.org (Arnd Bergmann)\0" - "Subject\0NVMe vs DMA addressing limitations\0" + "From\0Arnd Bergmann <arnd@linaro.org>\0" + "Subject\0Re: NVMe vs DMA addressing limitations\0" "Date\0Tue, 10 Jan 2017 16:02:28 +0100\0" + "To\0linux-arm-kernel@lists.infradead.org\0" + "Cc\0Christoph Hellwig <hch@lst.de>" + Nikita Yushchenko <nikita.yoush@cogentembedded.com> + Keith Busch <keith.busch@intel.com> + Sagi Grimberg <sagi@grimberg.me> + Jens Axboe <axboe@fb.com> + Catalin Marinas <catalin.marinas@arm.com> + Will Deacon <will.deacon@arm.com> + linux-kernel@vger.kernel.org + linux-nvme@lists.infradead.org + linux-renesas-soc@vger.kernel.org + Simon Horman <horms@verge.net.au> + linux-pci@vger.kernel.org + Bjorn Helgaas <bhelgaas@google.com> + " artemi.ivanov@cogentembedded.com\0" "\00:1\0" "b\0" "On Tuesday, January 10, 2017 3:48:39 PM CET Christoph Hellwig wrote:\n" - "> On Tue, Jan 10, 2017@12:01:05PM +0100, Arnd Bergmann wrote:\n" + "> On Tue, Jan 10, 2017 at 12:01:05PM +0100, Arnd Bergmann wrote:\n" "> > Another workaround me might need is to limit amount of concurrent DMA\n" "> > in the NVMe driver based on some platform quirk. The way that NVMe works,\n" "> > it can have very large amounts of data that is concurrently mapped into\n" @@ -36,4 +51,4 @@ "\n" "\tArnd" -833f6592331454b3fcbd44b2c7e0ad8e30e5699c21a83587cab5b52f3e64d301 +e0c01af8e514e58e1970e8d8a32ab24aef110c03b56bb9592e7e0d54f0f1b1e1
diff --git a/a/1.txt b/N3/1.txt index 5598285..cffd1ea 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -1,5 +1,5 @@ On Tuesday, January 10, 2017 3:48:39 PM CET Christoph Hellwig wrote: -> On Tue, Jan 10, 2017@12:01:05PM +0100, Arnd Bergmann wrote: +> On Tue, Jan 10, 2017 at 12:01:05PM +0100, Arnd Bergmann wrote: > > Another workaround me might need is to limit amount of concurrent DMA > > in the NVMe driver based on some platform quirk. The way that NVMe works, > > it can have very large amounts of data that is concurrently mapped into diff --git a/a/content_digest b/N3/content_digest index 07574a8..9111a83 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -4,10 +4,11 @@ "From\0arnd@linaro.org (Arnd Bergmann)\0" "Subject\0NVMe vs DMA addressing limitations\0" "Date\0Tue, 10 Jan 2017 16:02:28 +0100\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Tuesday, January 10, 2017 3:48:39 PM CET Christoph Hellwig wrote:\n" - "> On Tue, Jan 10, 2017@12:01:05PM +0100, Arnd Bergmann wrote:\n" + "> On Tue, Jan 10, 2017 at 12:01:05PM +0100, Arnd Bergmann wrote:\n" "> > Another workaround me might need is to limit amount of concurrent DMA\n" "> > in the NVMe driver based on some platform quirk. The way that NVMe works,\n" "> > it can have very large amounts of data that is concurrently mapped into\n" @@ -36,4 +37,4 @@ "\n" "\tArnd" -833f6592331454b3fcbd44b2c7e0ad8e30e5699c21a83587cab5b52f3e64d301 +ba16361808d72b04fca9ec5bfa5f0e5246c06a9b61f58a2ae0f7f58175e33407
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.