linux-ext4 - RE: Is it possible for the ext4/btrfs file system to pass some context related info to low level block driver?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CE761E84DADF2947A4AF22FB8D97A47358EE523B@shsmsx501.ccr.corp.intel.com>
Date:	Wed, 4 May 2011 18:31:19 +0800
From:	"Gao, Yunpeng" <yunpeng.gao@...el.com>
To:	Kyungmin Park <kmpark@...radead.org>
CC:	"linux-btrfs@...r.kernel.org" <linux-btrfs@...r.kernel.org>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>
Subject: RE: Is it possible for the ext4/btrfs file system to pass some
 context related info to low level block driver?

Hi Park,

Thanks a lot for the response.

>It seems similar with TRIM. So how about to consider TRIM
>implementation or extend it?

Yes, file system set REQ_DISCARD flag to notify block device driver to execute TRIM.
And I noticed there's already a flag REQ_META used for file system meta data.
But seems only gfs2 file system uses the REQ_META flag, other file systems (including ext4 and btrfs) have not used this flag.
Is the flag useless or any other reason?

>I'm not familiar with NCQ implementation but it's also helpful to implement it.

I don't know much about NCQ, too. Just have a impression that NCQ is only for SATA hard disk, can it also be used for block device, such as the mmc block device?

Thanks.

Regards,
Yunpeng

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html