From: Ric Wheeler <rwheeler@redhat.com>
To: Giridhar Yasa <giridhar.yasa@flipkart.com>, Sage Weil <sweil@redhat.com>
Cc: Shehbaz Jaffer <shehbazjaffer007@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: [GSoC2016] BlueStore SMR Support
Date: Mon, 14 Mar 2016 09:22:10 -0400 [thread overview]
Message-ID: <56E6BB02.6030801@redhat.com> (raw)
In-Reply-To: <CAKP7xVzKuwy9sP2PqJ-sHT0cygj6byuVX62=oUgnVCNpjWaE9A@mail.gmail.com>
On 03/14/2016 08:33 AM, Giridhar Yasa wrote:
> On Mon, Mar 14, 2016 at 5:47 PM, Sage Weil <sweil@redhat.com> wrote:
>> On Sun, 13 Mar 2016, Giridhar Yasa wrote:
>>> On Fri, Mar 11, 2016 at 8:20 PM, Sage Weil <sweil@redhat.com> wrote:
>>>> On Fri, 4 Mar 2016, Shehbaz Jaffer wrote:
>>>>
>>>>> 2) Will scope of project be to build an allocator on a simulator for
>>>>> SMR Drives? Or will I get actual HDDs to work with? In case of
>>>>> simulators, will the project involve building a simulator on disksim?
>>>> I seem to remember hearing something about a dm module that simulated SMR,
>>>> but I'm not sure. We may also be able to get some SMR disks to play
>>>> with--I'll reach out to our drive vendor friends.
>>> Would that be https://github.com/hgst/libzbc from HGST?
>> Yes.
>>
>> I'm not sure about a disk simulator or actual drive availability,
>> though.
> libzbc has an emulation mode that can use files or block devices to
> emulate SMR disk zones.
>
> Giridhar
>
Just keep in mind that different vendors have different behaviors - you will
need to tweak it I assume to make it act like the drive you are interested in.
Regards,
Ric
next prev parent reply other threads:[~2016-03-14 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 20:06 [GSoC2016] BlueStore SMR Support Shehbaz Jaffer
2016-03-11 14:50 ` Sage Weil
2016-03-12 20:07 ` Giridhar Yasa
2016-03-14 12:17 ` Sage Weil
2016-03-14 12:33 ` Giridhar Yasa
2016-03-14 12:40 ` Sage Weil
2016-03-14 13:22 ` Ric Wheeler [this message]
2016-03-14 16:42 ` Shehbaz Jaffer
2016-03-14 17:27 ` Ric Wheeler
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=56E6BB02.6030801@redhat.com \
--to=rwheeler@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=giridhar.yasa@flipkart.com \
--cc=shehbazjaffer007@gmail.com \
--cc=sweil@redhat.com \
/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.