From: Akinobu Mita <amgta@yacht.ocn.ne.jp>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Andrew Morton <akpm@zip.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mb_cache_shrink() frees unexpected caches
Date: Sat, 16 Jul 2005 12:53:12 +0900 [thread overview]
Message-ID: <1121485992.22941.4.camel@localhost.localdomain> (raw)
In-Reply-To: <200507160344.06235.agruen@suse.de>
2005-07-16 (Sat) 03:44 +0200 Andreas Gruenbacher wrote:
> Removing the cache parameter from mb_cache_shrink would break when more than
> one mb_cache is used per filesystem, correct. Leaving the parameter in and
> adding your patch is more "future proof", so I'm fine with it. Are you
> actually using more than one mb_cache, or is this theoretical?
This is just theorecal.
Now I agree with your two patches except for the name of
"mb_cache_shrink". it should be renamed to imply that this function
shrinks all sort of mbcache on specified block device.
prev parent reply other threads:[~2005-07-16 3:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 13:07 [PATCH] mb_cache_shrink() frees unexpected caches Akinobu Mita
2005-07-15 10:49 ` Andreas Gruenbacher
2005-07-15 13:41 ` Akinobu Mita
2005-07-15 14:36 ` Andreas Gruenbacher
2005-07-15 15:07 ` Akinobu Mita
2005-07-15 15:30 ` Akinobu Mita
2005-07-16 1:44 ` Andreas Gruenbacher
2005-07-16 3:53 ` Akinobu Mita [this message]
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=1121485992.22941.4.camel@localhost.localdomain \
--to=amgta@yacht.ocn.ne.jp \
--cc=agruen@suse.de \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.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.