Re: [PATCH V8 1/8] mm/fs: cleancache documentation

[OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>]

Dan Magenheimer <dan.magenheimer@oracle.com> writes:

>> 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.

Ah, mostly unused sb meant read once for all data pages on that sb for
each few days (updatedb might be wrong example, because it's meta
data. Umm... maybe likely example is backup process). I guess it will be
"put" all pages into backend, and would "flush" useful caches. So, I
think overhead and reclaim pressure are noticeable impact.

Ok, but if now it's concentrating on interface for backend of this, I
think it can be later.

>> 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 info.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>