linux-kernel - RE: [PATCH V8 1/8] mm/fs: cleancache documentation

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 for Android: free password hash cracker in your pocket

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

Message-ID: <67d72d8f-9809-4e43-9e90-417d4eb14db1@default>
Date:	Fri, 15 Apr 2011 12:37:11 -0700 (PDT)
From:	Dan Magenheimer <dan.magenheimer@...cle.com>
To:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
Cc:	Chris Mason <chris.mason@...cle.com>, viro@...iv.linux.org.uk,
	akpm@...ux-foundation.org, adilger.kernel@...ger.ca, tytso@....edu,
	mfasheh@...e.com, jlbec@...lplan.org, matthew@....cx,
	linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
	ocfs2-devel@....oracle.com, linux-mm@...ck.org, hch@...radead.org,
	ngupta@...are.org, jeremy@...p.org, JBeulich@...ell.com,
	Kurt Hackel <kurt.hackel@...cle.com>, npiggin@...nel.dk,
	Dave Mccracken <dave.mccracken@...cle.com>, riel@...hat.com,
	avi@...hat.com, Konrad Wilk <konrad.wilk@...cle.com>,
	mel@....ul.ie, yinghan@...gle.com, gthelen@...gle.com,
	torvalds@...ux-foundation.org
Subject: RE: [PATCH V8 1/8] mm/fs: cleancache documentation

Hi Hirofumi-san --

> Another question: why can't this enable/disable per sb, e.g. via mount
> options? (I have the interest the cache stuff like this by SSD on
> physical systems like dragonfly's swapcache.)

This would be useful and could be added later if individual
filesystems choose to add the mount functionality.  My goal with
this patchset is to enable only minimal functionality so
that other kernel developers can build on it.

> Well, anyway, I guess force enabling this for mostly unused sb can just
> add cache-write overhead and call for unpleasing reclaim to backend
> (because of limited space of backend) like updatedb.

If the sb is mostly unused, there should be few puts.  But you
are correct that if the backend has only very limited space,
cleancache adds cost and has little value.  On these systems,
cleancache should probably be disabled.  However, the cost
is very small so leaving it enabled may not even show a
measureable performance impact.

> And already there is in FAQ though, I also have interest about async
> interface because of SDD backend (I'm not sure for now though). Is
> there any plan like SSD backend?

Yes, I think an SSD backend is very interesting, especially
if the SSD is "very near" to the processor so that it can
be used as a RAM extension rather than as an I/O device.

The existing cleancache hooks will work for this and I am
working on a cleancache backend called RAMster that will
be a good foundation to access other asynchronous devices.
See: http://marc.info/?l=linux-mm&m=130013567810410&w=2 

Thanks for your feedback!
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/