From: Joel Becker <Joel.Becker@oracle.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Filesystem hints to storage
Date: Thu, 22 Jul 2010 12:15:41 -0700 [thread overview]
Message-ID: <20100722191541.GA12376@mail.oracle.com> (raw)
In-Reply-To: <20100722180854.GB22009@parisc-linux.org>
On Thu, Jul 22, 2010 at 12:08:54PM -0600, Matthew Wilcox wrote:
> 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.
If we're looking at the filesystem interface to all of this, I
would think these hints could be used by non-SSD storage as well.
Not only would a storage array benefit from knowing about random vs
sequential access, but expected redundancy hints would be huge in
managing utilization.
Joel
--
Life's Little Instruction Book #396
"Never give anyone a fruitcake."
Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-07-22 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 18:08 Filesystem hints to storage Matthew Wilcox
2010-07-22 19:15 ` Joel Becker [this message]
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=20100722191541.GA12376@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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.