Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1494726
| From | Christoph Hellwig <hch@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [Nbd] [PATCH][V3] nbd: add multi-connection support |
| Date | 2016-10-03 10:00 +0200 |
| Message-ID | <so6kh-1sc-9@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <snREB-Nm-7@gated-at.bofh.it> <snREB-Nm-5@gated-at.bofh.it> <so0yd-61L-1@gated-at.bofh.it> <so5Rf-13k-7@gated-at.bofh.it> <so6kh-1sc-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Oct 03, 2016 at 09:51:49AM +0200, Wouter Verhelst wrote: > Actually, I was pointing out the TCP head-of-line issue, where a delay > on the socket that contains the flush reply would result in the arrival > in the kernel block layer of a write reply before the said flush reply, > resulting in a write being considered part of the flush when in fact it > was not. The kernel (or any other user of SCSI/ATA/NVMe-like cache flushes) will wait for all I/O that needs to be in the cache for explicitly, so this is not a problem. > Can you clarify what you mean by that? Why is it an "odd flush > definition", and how would you "properly" define it? E.g. take the defintion from NVMe which also supports multiple queues: "The Flush command shall commit data and metadata associated with the specified namespace(s) to non-volatile media. The flush applies to all commands completed prior to the submission of the Flush command. The controller may also flush additional data and/or metadata from any namespace." The focus is completed - we need to get a reply to the host first before we can send the flush command, so anything that we require to be flushed needs to explicitly be completed first.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Wouter Verhelst <w@uter.be> - 2016-09-29 12:00 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Wouter Verhelst <w@uter.be> - 2016-09-29 18:50 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Alex Bligh <alex@alex.org.uk> - 2016-10-02 18:20 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Josef Bacik <jbacik@fb.com> - 2016-10-03 03:50 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Christoph Hellwig <hch@infradead.org> - 2016-10-03 09:30 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Wouter Verhelst <w@uter.be> - 2016-10-03 10:00 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Christoph Hellwig <hch@infradead.org> - 2016-10-03 10:00 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Alex Bligh <alex@alex.org.uk> - 2016-10-03 13:40 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Alex Bligh <alex@alex.org.uk> - 2016-10-03 16:50 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Wouter Verhelst <w@uter.be> - 2016-10-03 23:10 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Alex Bligh <alex@alex.org.uk> - 2016-10-04 11:40 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Wouter Verhelst <w@uter.be> - 2016-10-06 11:10 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Alex Bligh <alex@alex.org.uk> - 2016-10-06 11:50 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Wouter Verhelst <w@uter.be> - 2016-10-06 12:20 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Alex Bligh <alex@alex.org.uk> - 2016-10-06 13:10 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Christoph Hellwig <hch@infradead.org> - 2016-10-06 12:40 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Christoph Hellwig <hch@infradead.org> - 2016-10-06 15:20 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Wouter Verhelst <w@uter.be> - 2016-10-06 16:00 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Wouter Verhelst <w@uter.be> - 2016-10-06 15:20 +0200
Re: [Nbd] [PATCH][V3] nbd: add multi-connection support Wouter Verhelst <w@uter.be> - 2016-10-03 09:50 +0200
csiph-web