From: Matias Bjorling <m@bjorling.me>
To: Theodore Ts'o <tytso@mit.edu>, Damien Le Moal <damien.lemoal@wdc.com>
Cc: Slava Dubeyko <Vyacheslav.Dubeyko@wdc.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [LSF/MM TOPIC][LSF/MM ATTEND] OCSSDs - SMR, Hierarchical Interface, and Vector I/Os
Date: Tue, 10 Jan 2017 14:06:01 +0100 [thread overview]
Message-ID: <ddeefd67-afb6-72a4-f59b-6fe623fbfbc3@bjorling.me> (raw)
In-Reply-To: <20170110042442.ixxxi4yhj5gu7byh@thunk.org>
On 01/10/2017 05:24 AM, Theodore Ts'o wrote:
> This may be an area where if we can create the right framework, and
> fund some research work, we might be able to get some researchers and
> their graduate students interested in doing some work in figuring out
> what sort of divisions of responsibilities and hints back and forth
> between the storage device and host have the most benefit.
>
That is a good idea. There is a couple of papers at FAST with
Open-Channel SSDs this year. They look into the interface and various
ways to reduce latency fluctuations.
One thing I've heard a couple of times is the feature to move the GC
read/write process into the firmware. Enabling the host to offload GC
data movement, while the keeping the host in control. Would this be
beneficial for SMR?
-Matias
next prev parent reply other threads:[~2017-01-10 13:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 21:06 [LSF/MM TOPIC][LSF/MM ATTEND] OCSSDs - SMR, Hierarchical Interface, and Vector I/Os Matias Bjørling
2017-01-02 23:12 ` Viacheslav Dubeyko
2017-01-03 8:56 ` Matias Bjørling
2017-01-03 17:35 ` Viacheslav Dubeyko
2017-01-03 19:10 ` Matias Bjørling
2017-01-04 2:59 ` Slava Dubeyko
2017-01-04 7:24 ` Damien Le Moal
2017-01-04 12:39 ` Matias Bjørling
2017-01-04 16:57 ` Theodore Ts'o
2017-01-10 1:42 ` Damien Le Moal
2017-01-10 4:24 ` Theodore Ts'o
2017-01-10 13:06 ` Matias Bjorling [this message]
2017-01-11 4:07 ` Damien Le Moal
2017-01-11 6:06 ` Matias Bjorling
2017-01-11 7:49 ` Hannes Reinecke
2017-01-05 22:58 ` Slava Dubeyko
2017-01-06 1:11 ` Theodore Ts'o
2017-01-06 12:51 ` Matias Bjørling
2017-01-09 6:49 ` Slava Dubeyko
2017-01-09 14:55 ` Theodore Ts'o
2017-01-06 13:05 ` Matias Bjørling
2017-01-06 1:09 ` Jaegeuk Kim
2017-01-06 12:55 ` Matias Bjørling
2017-01-12 1:33 ` [LSF/MM " Damien Le Moal
2017-01-12 2:18 ` [Lsf-pc] " James Bottomley
2017-01-12 2:35 ` Damien Le Moal
2017-01-12 2:38 ` James Bottomley
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=ddeefd67-afb6-72a4-f59b-6fe623fbfbc3@bjorling.me \
--to=m@bjorling.me \
--cc=Vyacheslav.Dubeyko@wdc.com \
--cc=damien.lemoal@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=slava@dubeyko.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).