From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Damien Le Moal" <damien.lemoal@wdc.com>,
"Matias Bjørling" <m@bjorling.me>,
lsf-pc@lists.linux-foundation.org
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
linux-nvme@lists.infradead.org
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] OCSSDs - SMR, Hierarchical Interface, and Vector I/Os
Date: Wed, 11 Jan 2017 18:18:40 -0800 [thread overview]
Message-ID: <1484187520.2509.37.camel@HansenPartnership.com> (raw)
In-Reply-To: <e1c0b8e0-da91-563a-5913-a9a0db613ab3@wdc.com>
On Thu, 2017-01-12 at 10:33 +0900, Damien Le Moal wrote:
> Hello,
>
> A long discussion on the list followed this initial topic proposal
> from Matias. I think this is a worthy topic to discuss at LSF in
> order to steer development of the zoned block device interface in the
> right direction. Considering the relation and implication to ZBC/ZAC
> support,I would like to attend LSF/MM to participate in this
> discussion.
Just a note for the poor admin looking after the lists: to find all the
ATTEND and TOPIC requests for the lists I fold up the threads to the
top. If you frame your attend request as a reply, it's possible it
won't get counted because I didn't find it
so please *start a new thread* for ATTEND and TOPIC requests.
Thanks,
James
PS If you think you sent a TOPIC/ATTEND request in reply to something,
then I really haven't seen it because this is the first one I noticed,
and you should resend.
next prev parent reply other threads:[~2017-01-12 2:18 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
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 ` James Bottomley [this message]
2017-01-12 2:35 ` [Lsf-pc] " 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=1484187520.2509.37.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.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=m@bjorling.me \
/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).