All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Bdev claim and single writer semantics
Date: Wed, 02 May 2018 16:45:14 +0000	[thread overview]
Message-ID: <1525279502.1981.10.camel@intel.com> (raw)
In-Reply-To: CANvN+ekJRDSzqEyWOSK_fMsDTnThnJf5Du8pJRzWffuPQ_GLPg@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 459 bytes --]

On Wed, 2018-05-02 at 13:40 +0000, Andrey Kuzmin wrote:
> So how do we move this forward? Should I submit a patch based on the below
> approach, or just remove claimed check (and, presumably, leave bdev_open
> interface as is so that the caller can still limit access to read-only if
> desired)?

My vote (and Jim's) is to remove the check in spdk_bdev_claim. Don't change any
of the public APIs. If you submit a patch for this, we'll review and merge.

             reply	other threads:[~2018-05-02 16:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 16:45 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-09 21:57 [SPDK] Bdev claim and single writer semantics Walker, Benjamin
2018-05-09 17:58 Andrey Kuzmin
2018-05-09 17:32 Walker, Benjamin
2018-05-09  8:12 Andrey Kuzmin
2018-05-02 22:07 Andrey Kuzmin
2018-05-02 13:58 Luse, Paul E
2018-05-02 13:40 Andrey Kuzmin
2018-04-30 17:26 Andrey Kuzmin
2018-04-30 17:24 Walker, Benjamin
2018-04-28 21:35 Andrey Kuzmin
2018-04-28 21:30 Andrey Kuzmin
2018-04-28 21:13 Luse, Paul E
2018-04-27 23:06 Harris, James R
2018-04-27 15:04 Andrey Kuzmin
2018-04-26 23:26 Walker, Benjamin
2018-04-26 12:25 Andrey Kuzmin

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=1525279502.1981.10.camel@intel.com \
    --to=spdk@lists.01.org \
    /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.