Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Removing bs_dev
Date: Wed, 25 Jul 2018 17:26:37 +0000	[thread overview]
Message-ID: <5a321e4a3da6a6df584a2f6cdd32ba262ebda45a.camel@intel.com> (raw)
In-Reply-To: 122B872DCF83AB4DB816E25A2C1AD08D8BB4A3BD@IRSMSX102.ger.corp.intel.com

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

On Wed, 2018-07-25 at 04:44 +0000, Szwed, Maciej wrote:
> Hi,
> I was examining possibility of removing bs_dev layer from blobstore. As this
> would simplify code for basic blob/lvol usage, in case of snapshots and clones
> it would require whole new approach. Currently bs_dev layer is a basic
> mechanism for snapshots and clones interactions. I was thinking about some
> other ways we could build that relations w/o bs_dev, but I couldn’t find any
> good mechanism which would be simpler (or at least less complicated) than the
> current one. Therefore I don’t think that removing bs_dev is a good idea. If
> somebody have different thoughts on that or some ideas please let me know.


If removing the bs_dev from the clone/snapshot path doesn't result in a major
simplification, then it isn't worth doing. I thought that it might, since
blob_bs_dev.c could be removed entirely. But you still do need some abstraction
for handling what to do when a blob is thin provisioned and needs to return
zeroes, so maybe that negates any other simplifications. We can leave it low
priority and think about it for awhile.

Thanks,
Ben

             reply	other threads:[~2018-07-25 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 17:26 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-25  7:03 [SPDK] Removing bs_dev Yang, Ziye
2018-07-25  4:44 Szwed, Maciej

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=5a321e4a3da6a6df584a2f6cdd32ba262ebda45a.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox