linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Filesystem hints to storage
Date: Thu, 22 Jul 2010 12:08:54 -0600	[thread overview]
Message-ID: <20100722180854.GB22009@parisc-linux.org> (raw)


The NVMHCI working group has specified [1] a set of attributes for
filesystems to pass down to devices which may allow the device to lay
out its storage more effectively (eg if it's a hybrid MLC/SLC device).

For Enterprise NVMHCI, the working group is looking at refining these
hints.  Are there any hints that people would like to see added or
removed from the list in NVMHCI 1.0?

I think there are some hints that are hard for the filesystem to know
itself, never mind pass down, so it'd be good to remove them to reduce
the complexity.  Contrariwise, there are some hints I think the filesystem
could pass down that aren't in the spec today, such as the flags from
madvise (random access vs sequential access) and whether the access is
for fs metadata or application data.

[1] http://www.intel.com/standards/nvmhci/index.htm
Page 35, figure 26

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

             reply	other threads:[~2010-07-22 18:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 18:08 Matthew Wilcox [this message]
2010-07-22 19:15 ` Filesystem hints to storage Joel Becker
2010-07-22 19:45 ` Alan Cox
2010-07-26 15:40   ` 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=20100722180854.GB22009@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).