diff for duplicates of <1489526506.2676.13.camel@sandisk.com> diff --git a/a/1.txt b/N1/1.txt index 2a455ed..630fdb7 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,10 +1,8 @@ -On Mon, 2017-03-13 at 10:15 +0200, Sagi Grimberg wrote: -> > Additionally, I think making the hardware context an argument of this f= -unction -> > instead of using blk_mq_map_queue(q, smp_processor_id()) would make thi= -s +On Mon, 2017-03-13@10:15 +0200, Sagi Grimberg wrote: +> > Additionally, I think making the hardware context an argument of this function +> > instead of using blk_mq_map_queue(q, smp_processor_id()) would make this > > function much more versatile. ->=20 +> > What do you mean? remember that the callers interface to the device is > a request queue, it doesn't even know if its a blk-mq device. Can you > explain in more details what you would like to see? @@ -12,4 +10,4 @@ s Have you considered to make the CPU ID an argument instead of using the smp_processor_id() result? -Bart.= +Bart. diff --git a/a/content_digest b/N1/content_digest index 377b169..63f09d7 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,23 +2,16 @@ "ref\01489065402-14757-5-git-send-email-sagi@grimberg.me\0" "ref\01489076712.2597.1.camel@sandisk.com\0" "ref\0b8124df3-bd09-2eb2-9899-3c9195605510@grimberg.me\0" - "From\0Bart Van Assche <Bart.VanAssche@sandisk.com>\0" - "Subject\0Re: [PATCH rfc 04/10] block: Add a non-selective polling interface\0" + "From\0Bart.VanAssche@sandisk.com (Bart Van Assche)\0" + "Subject\0[PATCH rfc 04/10] block: Add a non-selective polling interface\0" "Date\0Tue, 14 Mar 2017 21:21:59 +0000\0" - "To\0linux-nvme@lists.infradead.org <linux-nvme@lists.infradead.org>" - linux-rdma@vger.kernel.org <linux-rdma@vger.kernel.org> - linux-block@vger.kernel.org <linux-block@vger.kernel.org> - target-devel@vger.kernel.org <target-devel@vger.kernel.org> - " sagi@grimberg.me <sagi@grimberg.me>\0" "\00:1\0" "b\0" - "On Mon, 2017-03-13 at 10:15 +0200, Sagi Grimberg wrote:\n" - "> > Additionally, I think making the hardware context an argument of this f=\n" - "unction\n" - "> > instead of using blk_mq_map_queue(q, smp_processor_id()) would make thi=\n" - "s\n" + "On Mon, 2017-03-13@10:15 +0200, Sagi Grimberg wrote:\n" + "> > Additionally, I think making the hardware context an argument of this function\n" + "> > instead of using blk_mq_map_queue(q, smp_processor_id()) would make this\n" "> > function much more versatile.\n" - ">=20\n" + "> \n" "> What do you mean? remember that the callers interface to the device is\n" "> a request queue, it doesn't even know if its a blk-mq device. Can you\n" "> explain in more details what you would like to see?\n" @@ -26,6 +19,6 @@ "Have you considered to make the CPU ID an argument instead of using the\n" "smp_processor_id() result?\n" "\n" - Bart.= + Bart. -ad7a0d00eb8ad68cf0a2ae6341812f482333d8452eaaf6ab5c386b75cc120ef7 +50dc1f8cd000b6a598b2f3a20870c7d256a9c848f7504432eb7a2f1117073eba
diff --git a/a/1.txt b/N2/1.txt index 2a455ed..d9ab543 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,10 +1,8 @@ On Mon, 2017-03-13 at 10:15 +0200, Sagi Grimberg wrote: -> > Additionally, I think making the hardware context an argument of this f= -unction -> > instead of using blk_mq_map_queue(q, smp_processor_id()) would make thi= -s +> > Additionally, I think making the hardware context an argument of this function +> > instead of using blk_mq_map_queue(q, smp_processor_id()) would make this > > function much more versatile. ->=20 +> > What do you mean? remember that the callers interface to the device is > a request queue, it doesn't even know if its a blk-mq device. Can you > explain in more details what you would like to see? @@ -12,4 +10,7 @@ s Have you considered to make the CPU ID an argument instead of using the smp_processor_id() result? -Bart.= +Bart.-- +To unsubscribe from this list: send the line "unsubscribe linux-rdma" in +the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N2/content_digest index 377b169..1c327cd 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,23 +2,22 @@ "ref\01489065402-14757-5-git-send-email-sagi@grimberg.me\0" "ref\01489076712.2597.1.camel@sandisk.com\0" "ref\0b8124df3-bd09-2eb2-9899-3c9195605510@grimberg.me\0" - "From\0Bart Van Assche <Bart.VanAssche@sandisk.com>\0" + "ref\0b8124df3-bd09-2eb2-9899-3c9195605510-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org\0" + "From\0Bart Van Assche <Bart.VanAssche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>\0" "Subject\0Re: [PATCH rfc 04/10] block: Add a non-selective polling interface\0" "Date\0Tue, 14 Mar 2017 21:21:59 +0000\0" - "To\0linux-nvme@lists.infradead.org <linux-nvme@lists.infradead.org>" - linux-rdma@vger.kernel.org <linux-rdma@vger.kernel.org> - linux-block@vger.kernel.org <linux-block@vger.kernel.org> - target-devel@vger.kernel.org <target-devel@vger.kernel.org> - " sagi@grimberg.me <sagi@grimberg.me>\0" + "To\0linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>" + linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + target-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <target-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + " sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>\0" "\00:1\0" "b\0" "On Mon, 2017-03-13 at 10:15 +0200, Sagi Grimberg wrote:\n" - "> > Additionally, I think making the hardware context an argument of this f=\n" - "unction\n" - "> > instead of using blk_mq_map_queue(q, smp_processor_id()) would make thi=\n" - "s\n" + "> > Additionally, I think making the hardware context an argument of this function\n" + "> > instead of using blk_mq_map_queue(q, smp_processor_id()) would make this\n" "> > function much more versatile.\n" - ">=20\n" + "> \n" "> What do you mean? remember that the callers interface to the device is\n" "> a request queue, it doesn't even know if its a blk-mq device. Can you\n" "> explain in more details what you would like to see?\n" @@ -26,6 +25,9 @@ "Have you considered to make the CPU ID an argument instead of using the\n" "smp_processor_id() result?\n" "\n" - Bart.= + "Bart.--\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-rdma\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -ad7a0d00eb8ad68cf0a2ae6341812f482333d8452eaaf6ab5c386b75cc120ef7 +c7d5463b31b589dd02fc955c6a6dab3508346565a376b2f39776f25643aa35e1
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.