diff for duplicates of <1484151982.2619.6.camel@sandisk.com> diff --git a/a/1.txt b/N1/1.txt index 0a6efc2..7c3883d 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,16 +1,15 @@ -On Wed, 2017-01-11 at 17:22 +0100, Hannes Reinecke wrote: +On Wed, 2017-01-11@17:22 +0100, Hannes Reinecke wrote: > On 01/11/2017 05:12 PM, hch@infradead.org wrote: -> > On Wed, Jan 11, 2017 at 04:08:31PM +0000, Bart Van Assche wrote: +> > On Wed, Jan 11, 2017@04:08:31PM +0000, Bart Van Assche wrote: > > > A typical Ethernet network adapter delays the generation of an > > > interrupt -> > > after it has received a packet. A typical block device or HBA does no= -t +> > > after it has received a packet. A typical block device or HBA does not > > > delay > > > the generation of an interrupt that reports an I/O completion. -> >=20 +> > > > NVMe allows for configurable interrupt coalescing, as do a few modern > > SCSI HBAs. ->=20 +> > Essentially every modern SCSI HBA does interrupt coalescing; otherwise > the queuing interface won't work efficiently. @@ -21,4 +20,4 @@ block device for which interrupt coalescing was not enabled. I think that the measurements have to be repeated against a block device for which interrupt coalescing is enabled. -Bart.= +Bart. diff --git a/a/content_digest b/N1/content_digest index 65e25c7..4f9e903 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,33 +2,23 @@ "ref\01484150893.2619.1.camel@sandisk.com\0" "ref\020170111161238.GA18881@infradead.org\0" "ref\02aff05af-5e83-7d3d-f879-2cce02b6d88c@suse.de\0" - "From\0Bart Van Assche <Bart.VanAssche@sandisk.com>\0" - "Subject\0Re: [LSF/MM TOPIC][LSF/MM ATTEND] NAPI polling for block drivers\0" + "From\0Bart.VanAssche@sandisk.com (Bart Van Assche)\0" + "Subject\0[LSF/MM TOPIC][LSF/MM ATTEND] NAPI polling for block drivers\0" "Date\0Wed, 11 Jan 2017 16:26:40 +0000\0" - "To\0hch@infradead.org <hch@infradead.org>" - " hare@suse.de <hare@suse.de>\0" - "Cc\0Linux-scsi@vger.kernel.org <Linux-scsi@vger.kernel.org>" - keith.busch@intel.com <keith.busch@intel.com> - jthumshirn@suse.de <jthumshirn@suse.de> - linux-nvme@lists.infradead.org <linux-nvme@lists.infradead.org> - lsf-pc@lists.linux-foundation.org <lsf-pc@lists.linux-foundation.org> - linux-block@vger.kernel.org <linux-block@vger.kernel.org> - " sagi@grimberg.me <sagi@grimberg.me>\0" "\00:1\0" "b\0" - "On Wed, 2017-01-11 at 17:22 +0100, Hannes Reinecke wrote:\n" + "On Wed, 2017-01-11@17:22 +0100, Hannes Reinecke wrote:\n" "> On 01/11/2017 05:12 PM, hch@infradead.org wrote:\n" - "> > On Wed, Jan 11, 2017 at 04:08:31PM +0000, Bart Van Assche wrote:\n" + "> > On Wed, Jan 11, 2017@04:08:31PM +0000, Bart Van Assche wrote:\n" "> > > A typical Ethernet network adapter delays the generation of an\n" "> > > interrupt\n" - "> > > after it has received a packet. A typical block device or HBA does no=\n" - "t\n" + "> > > after it has received a packet. A typical block device or HBA does not\n" "> > > delay\n" "> > > the generation of an interrupt that reports an I/O completion.\n" - "> >=20\n" + "> > \n" "> > NVMe allows for configurable interrupt coalescing, as do a few modern\n" "> > SCSI HBAs.\n" - ">=20\n" + "> \n" "> Essentially every modern SCSI HBA does interrupt coalescing; otherwise\n" "> the queuing interface won't work efficiently.\n" "\n" @@ -39,6 +29,6 @@ "the measurements have to be repeated against a block device for which\n" "interrupt coalescing is enabled.\n" "\n" - Bart.= + Bart. -ebbb332661ffc8694e9992b4294fae0f531545ac089336ece52a4f1cce940587 +4aa9040d4dc4fd5221556ecd8527e0f1c74626a83f2a092b84314b3790d39c50
diff --git a/a/1.txt b/N2/1.txt index 0a6efc2..678e068 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -3,14 +3,13 @@ On Wed, 2017-01-11 at 17:22 +0100, Hannes Reinecke wrote: > > On Wed, Jan 11, 2017 at 04:08:31PM +0000, Bart Van Assche wrote: > > > A typical Ethernet network adapter delays the generation of an > > > interrupt -> > > after it has received a packet. A typical block device or HBA does no= -t +> > > after it has received a packet. A typical block device or HBA does not > > > delay > > > the generation of an interrupt that reports an I/O completion. -> >=20 +> > > > NVMe allows for configurable interrupt coalescing, as do a few modern > > SCSI HBAs. ->=20 +> > Essentially every modern SCSI HBA does interrupt coalescing; otherwise > the queuing interface won't work efficiently. @@ -21,4 +20,4 @@ block device for which interrupt coalescing was not enabled. I think that the measurements have to be repeated against a block device for which interrupt coalescing is enabled. -Bart.= +Bart. diff --git a/a/content_digest b/N2/content_digest index 65e25c7..4ae86f0 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -21,14 +21,13 @@ "> > On Wed, Jan 11, 2017 at 04:08:31PM +0000, Bart Van Assche wrote:\n" "> > > A typical Ethernet network adapter delays the generation of an\n" "> > > interrupt\n" - "> > > after it has received a packet. A typical block device or HBA does no=\n" - "t\n" + "> > > after it has received a packet. A typical block device or HBA does not\n" "> > > delay\n" "> > > the generation of an interrupt that reports an I/O completion.\n" - "> >=20\n" + "> > \n" "> > NVMe allows for configurable interrupt coalescing, as do a few modern\n" "> > SCSI HBAs.\n" - ">=20\n" + "> \n" "> Essentially every modern SCSI HBA does interrupt coalescing; otherwise\n" "> the queuing interface won't work efficiently.\n" "\n" @@ -39,6 +38,6 @@ "the measurements have to be repeated against a block device for which\n" "interrupt coalescing is enabled.\n" "\n" - Bart.= + Bart. -ebbb332661ffc8694e9992b4294fae0f531545ac089336ece52a4f1cce940587 +baaaa6344d7338bfb1b93c0b05845129d271443408fea9e39ed239f49c80f7c5
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.