linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@us.ibm.com>
To: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: [LSF/MM TOPIC] Utilizing T10/DIF in Filesystems
Date: Wed, 9 Feb 2011 12:00:35 -0800	[thread overview]
Message-ID: <20110209200035.GG27190@tux1.beaverton.ibm.com> (raw)

I would like to talk about the status and future direction of T10/DIF support
in the kernel.  Here's something resembling an abstract:

Utilizing T10/DIF in Filesystems

For quite some time, we've been discussing the inclusion of T10/DIF
functionality into the kernel to associate a small amount of checksum/integrity
data with each sector.  Now that actual hardware is appearing on the market, it
is time to take another look at what we can do with this feature.

We'd like to discuss at least a few specific topics:

1. How to resolve the write-after-checksum problem (if we haven't fixed it by then).
2. How do we expose a API that enables userspace to read and write  application
   tags that go with a file's data blocks?
3. How could we make use of the application tag for metadata blocks?
4. A 16-bit application tag is rather small.  What could we do with DIF if that
   tag were bigger, and how could we make that happen?

--D

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2011-02-09 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 20:00 Darrick J. Wong [this message]
2011-02-10 23:07 ` [LSF/MM TOPIC] Utilizing T10/DIF in Filesystems Joel Becker

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=20110209200035.GG27190@tux1.beaverton.ibm.com \
    --to=djwong@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.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).