All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wouter Verhelst <w@uter.be>
To: Christoph Hellwig <hch@infradead.org>
Cc: "nbd-general@lists.sourceforge.net"
	<nbd-general@lists.sourceforge.net>, Josef Bacik <jbacik@fb.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jens Axboe <axboe@fb.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Kernel Team <Kernel-team@fb.com>
Subject: Re: [Nbd] [PATCH][V3] nbd: add multi-connection support
Date: Thu, 6 Oct 2016 15:09:49 +0200	[thread overview]
Message-ID: <20161006130949.nk7gsy6lpw5kudbg@grep.be> (raw)
In-Reply-To: <20161006103155.GA20279@infradead.org>

On Thu, Oct 06, 2016 at 03:31:55AM -0700, Christoph Hellwig wrote:
> No, they match the cache flush semantics in every other storage protocol
> known to me, and they match the expectations of both the Linux kernel
> and any other OS or comsumer I know about perfectly.

Okay, I've updated the proto.md file then, to clarify that in the case
of multiple connections, a client MUST NOT send a flush request until it
has seen the replies to the write requests that it cares about. That
should be enough for now.

Thanks,

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
       people in the world who think they really understand all of its rules,
       and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12

  reply	other threads:[~2016-10-06 13:10 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28 20:01 [PATCH][V3] nbd: add multi-connection support Josef Bacik
2016-09-29  9:52 ` [Nbd] " Wouter Verhelst
2016-09-29 14:03   ` Josef Bacik
2016-09-29 16:41     ` Wouter Verhelst
2016-09-29 16:59       ` Josef Bacik
2016-10-02 16:17         ` Alex Bligh
2016-10-02 16:17           ` Alex Bligh
2016-10-03  1:47           ` Josef Bacik
2016-10-03  1:47             ` Josef Bacik
2016-10-03  7:20             ` Christoph Hellwig
2016-10-03  7:20               ` Christoph Hellwig
2016-10-03  7:51               ` Wouter Verhelst
2016-10-03  7:51                 ` Wouter Verhelst
2016-10-03  7:57                 ` Christoph Hellwig
2016-10-03  7:57                   ` Christoph Hellwig
2016-10-03 11:34                   ` Alex Bligh
2016-10-03 11:34                     ` Alex Bligh
2016-10-03 14:32                     ` Josef Bacik
2016-10-03 14:32                       ` Josef Bacik
2016-10-03 14:46                       ` Alex Bligh
2016-10-03 14:46                         ` Alex Bligh
2016-10-03 21:07                     ` Wouter Verhelst
2016-10-03 21:07                       ` Wouter Verhelst
2016-10-04  9:35                       ` Alex Bligh
2016-10-04  9:35                         ` Alex Bligh
2016-10-06  9:04                         ` Wouter Verhelst
2016-10-06  9:04                           ` Wouter Verhelst
2016-10-06  9:41                           ` Alex Bligh
2016-10-06  9:41                             ` Alex Bligh
2016-10-06 10:15                             ` Wouter Verhelst
2016-10-06 10:15                               ` Wouter Verhelst
2016-10-06 11:04                               ` Alex Bligh
2016-10-06 11:04                                 ` Alex Bligh
2016-10-06 10:31                           ` Christoph Hellwig
2016-10-06 10:31                             ` Christoph Hellwig
2016-10-06 13:09                             ` Wouter Verhelst [this message]
2016-10-06 13:09                               ` Wouter Verhelst
2016-10-06 13:16                               ` Christoph Hellwig
2016-10-06 13:16                                 ` Christoph Hellwig
2016-10-06 13:55                                 ` Wouter Verhelst
2016-10-06 13:55                                   ` Wouter Verhelst
2016-10-03  7:49           ` Wouter Verhelst
2016-10-03  7:49             ` Wouter Verhelst
2016-10-11  9:00 ` Sagi Grimberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161006130949.nk7gsy6lpw5kudbg@grep.be \
    --to=w@uter.be \
    --cc=Kernel-team@fb.com \
    --cc=axboe@fb.com \
    --cc=hch@infradead.org \
    --cc=jbacik@fb.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbd-general@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.