From: Sasha Levin <sasha.levin@oracle.com>
To: Adrian Palmer <adrian.palmer@seagate.com>,
lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] - SMR Modifications to EXT4 (and other generic file systems)
Date: Wed, 07 Jan 2015 09:57:47 -0500 [thread overview]
Message-ID: <54AD496B.8080708@oracle.com> (raw)
In-Reply-To: <CAKdFiL6CMHTHWCvSFjFNw6hzvPLDEWWAC-o3wdivq9co7SX1FA@mail.gmail.com>
On 01/06/2015 06:29 PM, Adrian Palmer wrote:
> I'd like to host a discussion of SMRFFS and ZAC for consumer and cloud
> systems at LSF/MM. I want to gather community consensus at LSF/MM of the
> required technical kernel changes before this topic is presented at Vault.
>
> Subtopics:
>
> On-disk metadata structures and data algorithms
> Explicit in-order write requirement and a look at the IO stack
> New IOCTLs to call from the FS and the need to know about the underlying
> disk -- no longer completely disk agnostic
Where can we read about the details of SMRFFS before LSF/MM / Vault?
Thanks,
Sasha
next parent reply other threads:[~2015-01-07 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKdFiL6CMHTHWCvSFjFNw6hzvPLDEWWAC-o3wdivq9co7SX1FA@mail.gmail.com>
2015-01-07 14:57 ` Sasha Levin [this message]
2015-01-10 13:40 ` [Lsf-pc] [LSF/MM TOPIC] - SMR Modifications to EXT4 (and other generic file systems) Hannes Reinecke
2015-01-13 20:32 ` Adrian Palmer
2015-01-13 21:50 ` Andreas Dilger
2015-01-13 23:26 ` Adrian Palmer
2015-02-15 20:27 ` Alireza Haghdoost
2015-02-16 5:02 ` Adrian Palmer
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=54AD496B.8080708@oracle.com \
--to=sasha.levin@oracle.com \
--cc=adrian.palmer@seagate.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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 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).