linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kyungmin Park <kmpark@infradead.org>
To: "Gao, Yunpeng" <yunpeng.gao@intel.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: Is it possible for the ext4/btrfs file system to pass some context related info to low level block driver?
Date: Tue, 3 May 2011 13:10:26 +0900	[thread overview]
Message-ID: <BANLkTikm-ZMG7KRjjz0DtduPDC4KUw7_Bg@mail.gmail.com> (raw)
In-Reply-To: <CE761E84DADF2947A4AF22FB8D97A47358E28022@shsmsx501.ccr.corp.intel.com>

Hi,

It seems similar with TRIM. So how about to consider TRIM
implementation or extend it?
I'm not familiar with NCQ implementation but it's also helpful to imple=
ment it.

Thank you,
Kyungmin Park

On Tue, May 3, 2011 at 11:44 AM, Gao, Yunpeng <yunpeng.gao@intel.com> w=
rote:
> Currently, some new storage devices have the ability to do performanc=
e optimizations according to the type of data payload - say, file syste=
m metadata, time-stamps, sequential write in some granularity, random w=
rite and so on.
>
> For example, the latest eMMC 4.5 device can support the so-called 'Co=
ntext Management' and 'Data Tag Mechanism' features. By receiving the i=
nformation of payload data type, the eMMC 4.5 device can improve the ac=
cess rate during the following read and update operations and offer a m=
ore reliable and robust storage.
>
> And obviously, to enable these kind of advanced features of storage d=
evice, it needs not only the low level block device driver supports, bu=
t also the file system supports since files system knows more info abou=
t the data type of the payload. But currently, seems there are no file =
systems implemented these kind of supports yet.
>
> So, my question is, is there any plan or discussion on supporting thi=
s feature (passing data type info to low level block device driver) on =
file system developments? Especially for ext4/btrfs, since now they are=
 very hot in Linux? Thanks.
>
>
> Regards,
> Yunpeng Gao
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" =
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel=
" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-05-03  4:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03  2:44 Is it possible for the ext4/btrfs file system to pass some context related info to low level block driver? Gao, Yunpeng
2011-05-03  4:10 ` Kyungmin Park [this message]
2011-05-04 10:31   ` Gao, Yunpeng
2011-05-03 13:43 ` Martin K. Petersen
2011-05-04 11:45   ` Gao, Yunpeng
2011-05-04 14:51     ` Andreas Dilger
2011-05-05 18:10       ` Matthew Wilcox
2011-05-05 20:11         ` Andreas Dilger
2011-05-09  5:50       ` Gao, Yunpeng

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=BANLkTikm-ZMG7KRjjz0DtduPDC4KUw7_Bg@mail.gmail.com \
    --to=kmpark@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=yunpeng.gao@intel.com \
    /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).