All of lore.kernel.org
 help / color / mirror / Atom feed
From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Cleancache
Date: Wed, 8 Jun 2011 15:14:59 +0200	[thread overview]
Message-ID: <201106081514.59693.dexen.devries@gmail.com> (raw)

Hi list,


there's that recent interesting addition to linux: `cleancache' (and 
`zcache').
I've enabled it for NILFS2 yesterday (in 3.0-rc2).
It seemed to work for a while -- sensible numbers in 
/sys/kernel/mm/cleancache/* 
But it broke terribly after performing
echo 3 > /proc/sys/vm/drop_caches
kernel reported NULL pointer dereference, IIRC. Ext4 works a-OK with that, so 
my first guess waws NILFS2 is doing something funky with page allocation or 
mapping.

Cleancache has own hooks into VFS, and for `normal' filesystem that's enough; 
at least enough for ext3 and ext4 drivers to work reliably. On the other hand, 
btrfs does something unusual with pages and they used extra cleancache hooks 
for btrfs, IIRC.

Should I dig further, post backtraces or something?

I believe using cleancache + zcache could be beneficial, especially for NILFS2 
metadata like the DAT file; what are your thoughts on it?


Regards,
-- 
dexen deVries

[[[↓][→]]]

For example, if the first thing in the file is:
   <?kzy irefvba="1.0" rapbqvat="ebg13"?>
an XML parser will recognize that the document is stored in the traditional 
ROT13 encoding.

(( Joe English, http://www.flightlab.com/~joe/sgml/faq-not.txt ))
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2011-06-08 13:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 13:14 dexen deVries [this message]
     [not found] ` <201106081514.59693.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-08 14:02   ` Cleancache Ryusuke Konishi
     [not found]     ` <20110608.230231.65968027.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-06-13 13:15       ` Cleancache Ryusuke Konishi
     [not found]         ` <20110613.221503.212701772.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-06-13 13:21           ` Cleancache dexen deVries
     [not found]             ` <201106131521.15372.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-13 14:40               ` Cleancache Ryusuke Konishi
     [not found]                 ` <20110613.234048.21322431.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-06-13 17:54                   ` Cleancache dexen deVries
2011-06-13 18:04                   ` Cleancache [2] dexen deVries
     [not found]                     ` <201106132004.41118.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-14 16:17                       ` Ryusuke Konishi
     [not found]                         ` <BANLkTikdQLrp3EMGq=BV83BQKKkN1Emdcw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-20 18:16                           ` Ryusuke Konishi
2011-06-13 18:08                   ` Cleancache [3/3] dexen deVries
2011-06-13 22:38                   ` Cleancache [kernel config] dexen deVries

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=201106081514.59693.dexen.devries@gmail.com \
    --to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.