From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andreas Dilger <adilger@dilger.ca>, lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] status update on stream IDs
Date: Fri, 06 Jan 2017 16:05:49 -0800 [thread overview]
Message-ID: <1483747549.7432.6.camel@HansenPartnership.com> (raw)
In-Reply-To: <E86FC13D-0058-473C-B9D6-36B988ABEFFE@dilger.ca>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
On Fri, 2017-01-06 at 16:54 -0700, Andreas Dilger wrote:
> At LSF/MM'16 and Linux FAST (https://lwn.net/Articles/685499/) there
> were discussions about adding stream IDs to the block/device layer to
> allow higher layers (filesystems, applications) to identify IO
> streams so lower layers (SSDs, hybrid storage, etc.) can make better
> allocation/placement decisions.
>
> It would be useful to get an update on the state of this work, and
> discuss any obstacles that need to be resolved for getting this code
> landed.
OK, so I'm a bit at a loss for how to add this one to the spreadsheet.
Usually people propose topics *they* would like to talk about. Since
this is a topic you want to hear about, did you have anyone in mind to
be the speaker on this topic?
James
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-01-07 0:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 23:54 [LSF/MM TOPIC] status update on stream IDs Andreas Dilger
2017-01-06 23:58 ` Andreas Dilger
2017-01-06 23:58 ` Andreas Dilger
2017-01-06 23:58 ` Andreas Dilger
2017-01-07 1:38 ` Kwan (Hingkwan) Huen
2017-01-07 1:38 ` Kwan (Hingkwan) Huen
2017-01-07 1:38 ` Kwan (Hingkwan) Huen
[not found] ` <87B8B7C67ECB1048AE5FA3C64D62B73E1CA9473A@SSIEXCH-MB3.ssi.samsung.com>
2017-01-07 2:06 ` Changho Choi
2017-01-07 2:06 ` Changho Choi
2017-01-07 2:06 ` Changho Choi
2017-01-07 0:05 ` James Bottomley [this message]
2017-01-07 0:13 ` [Lsf-pc] " Andreas Dilger
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=1483747549.7432.6.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=adilger@dilger.ca \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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.