All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20181114013630.GB14592@redhat.com>

diff --git a/a/1.txt b/N1/1.txt
index f5b5615..8edc073 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -7,7 +7,7 @@ Mike Snitzer <snitzer@redhat.com> wrote:
 > > On 11/13/18 5:41 PM, Guenter Roeck wrote:
 > > > Hi,
 > > > 
-> > > On Wed, Oct 31, 2018@08:36:31AM -0600, Jens Axboe wrote:
+> > > On Wed, Oct 31, 2018 at 08:36:31AM -0600, Jens Axboe wrote:
 > > >> NVMe does round-robin between queues by default, which means that
 > > >> sharing a queue map for both reads and writes can be problematic
 > > >> in terms of read servicing. It's much easier to flood the queue
@@ -23,9 +23,9 @@ Mike Snitzer <snitzer@redhat.com> wrote:
 > > >> one for writes, the latter using the configurable number of
 > > >> queues (hardware queue counts permitting).
 > > >>
-> > >> Reviewed-by: Hannes Reinecke <hare at suse.com>
-> > >> Reviewed-by: Keith Busch <keith.busch at intel.com>
-> > >> Signed-off-by: Jens Axboe <axboe at kernel.dk>
+> > >> Reviewed-by: Hannes Reinecke <hare@suse.com>
+> > >> Reviewed-by: Keith Busch <keith.busch@intel.com>
+> > >> Signed-off-by: Jens Axboe <axboe@kernel.dk>
 > > > 
 > > > This patch causes hangs when running recent versions of
 > > > -next with several architectures; see the -next column at
diff --git a/a/content_digest b/N1/content_digest
index 1f4d266..9a0c98b 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,9 +1,15 @@
  "ref\020181114004148.GA29545@roeck-us.net\0"
  "ref\0f1e91342-2b04-6d9f-e77a-6e812c6888d0@kernel.dk\0"
  "ref\020181114012810.GA14592@redhat.com\0"
- "From\0snitzer@redhat.com (Mike Snitzer)\0"
- "Subject\0nvme: utilize two queue maps, one for reads and one for writes\0"
+ "From\0Mike Snitzer <snitzer@redhat.com>\0"
+ "Subject\0Re: nvme: utilize two queue maps, one for reads and one for writes\0"
  "Date\0Tue, 13 Nov 2018 20:36:30 -0500\0"
+ "To\0Jens Axboe <axboe@kernel.dk>\0"
+ "Cc\0Guenter Roeck <linux@roeck-us.net>"
+  Keith Busch <keith.busch@intel.com>
+  Sagi Grimberg <sagi@grimberg.me>
+  linux-nvme@lists.infradead.org
+ " linux-kernel@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On Tue, Nov 13 2018 at  8:28pm -0500,\n"
@@ -15,7 +21,7 @@
  "> > On 11/13/18 5:41 PM, Guenter Roeck wrote:\n"
  "> > > Hi,\n"
  "> > > \n"
- "> > > On Wed, Oct 31, 2018@08:36:31AM -0600, Jens Axboe wrote:\n"
+ "> > > On Wed, Oct 31, 2018 at 08:36:31AM -0600, Jens Axboe wrote:\n"
  "> > >> NVMe does round-robin between queues by default, which means that\n"
  "> > >> sharing a queue map for both reads and writes can be problematic\n"
  "> > >> in terms of read servicing. It's much easier to flood the queue\n"
@@ -31,9 +37,9 @@
  "> > >> one for writes, the latter using the configurable number of\n"
  "> > >> queues (hardware queue counts permitting).\n"
  "> > >>\n"
- "> > >> Reviewed-by: Hannes Reinecke <hare at suse.com>\n"
- "> > >> Reviewed-by: Keith Busch <keith.busch at intel.com>\n"
- "> > >> Signed-off-by: Jens Axboe <axboe at kernel.dk>\n"
+ "> > >> Reviewed-by: Hannes Reinecke <hare@suse.com>\n"
+ "> > >> Reviewed-by: Keith Busch <keith.busch@intel.com>\n"
+ "> > >> Signed-off-by: Jens Axboe <axboe@kernel.dk>\n"
  "> > > \n"
  "> > > This patch causes hangs when running recent versions of\n"
  "> > > -next with several architectures; see the -next column at\n"
@@ -64,4 +70,4 @@
  "  struct rq *rq;\n"
               ^~
 
-96c0ca90d1f52cc76b06e2ba9911edb158c5c8c15c4a28c02b5bbbdca4800f5d
+bb630aa1d456d0658f81d91d73b33fe85e0f5560cd0e9cc16980127e52829835

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.