From: Joe Thornber <thornber@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Mike Snitzer <msnitzer@redhat.com>,
dm-devel@redhat.com, "Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: dm-bufio cache patches
Date: Thu, 9 Oct 2014 14:07:36 +0100 [thread overview]
Message-ID: <20141009130736.GA21297@debian> (raw)
In-Reply-To: <alpine.LRH.2.02.1410081617120.9823@file01.intranet.prod.int.rdu2.redhat.com>
On Wed, Oct 08, 2014 at 04:17:59PM -0400, Mikulas Patocka wrote:
> > I created dm-bufio patchset that keep some amount of cache indefinitely,
> > regardless of the timeout (the default is to keep 1/500 of total memory
> > indefinitely).
I'm running something similar here. I just put in a hard coded
default rather than basing it on the amount of memory present. I'm
not sure which I prefer.
I've also switched over to using a rbtree instead of that huge hash
table which consumes 8m.
I'll post clean patches in a bit.
- Joe
next prev parent reply other threads:[~2014-10-09 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 20:10 dm-bufio cache patches Mikulas Patocka
2014-10-08 20:17 ` Mikulas Patocka
2014-10-09 13:07 ` Joe Thornber [this message]
2014-10-09 15:40 ` Mikulas Patocka
2014-10-13 9:02 ` Joe Thornber
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=20141009130736.GA21297@debian \
--to=thornber@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@redhat.com \
--cc=msnitzer@redhat.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