From: Ed Tomlinson <tomlins@cam.org>
To: Craig Kulesa <ckulesa@as.arizona.edu>
Cc: Steven Cole <elenstev@mesatop.com>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
Steven Cole <scole@lanl.gov>
Subject: Re: [PATCH 2/2] move slab pages to the lru, for 2.5.27
Date: Mon, 22 Jul 2002 20:21:51 -0400 [thread overview]
Message-ID: <200207222021.51600.tomlins@cam.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0207221520301.14311-100000@loke.as.arizona.edu>
Craig Kulesa wrote:
> On another note -- Steven did point out that the slablru patch has a
> patchbug with regards to dquot.c. I think this error is also in Ed's
> June 5th patch (at least as posted), and I didn't catch it.
> I believe that:
>
> shrink_dqcache_memory(int priority, unsigned int gfp_mask)
> needs to be
> age_dqcache_memory(kmem_cache_t *cachep, int entries, int gfp_mask)
>
> in dquot.c. It'll be tested and fixed on the next go. :)
Right. Fixed in the linux-2.4-rmap bk tree with slablru at casa.dyndns.org:3334
Thanks
Ed Tomlinson
next prev parent reply other threads:[~2002-07-23 0:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 11:24 [PATCH 2/2] move slab pages to the lru, for 2.5.27 Craig Kulesa
2002-07-21 13:33 ` Ed Tomlinson
2002-07-21 21:24 ` Craig Kulesa
2002-07-21 23:15 ` Ed Tomlinson
2002-07-21 21:31 ` William Lee Irwin III
2002-07-22 7:08 ` Craig Kulesa
2002-07-22 18:54 ` Steven Cole
2002-07-22 22:17 ` Ed Tomlinson
2002-07-22 22:21 ` William Lee Irwin III
2002-07-22 22:36 ` Craig Kulesa
2002-07-23 0:21 ` Ed Tomlinson [this message]
2002-07-23 4:36 ` William Lee Irwin III
2002-07-23 11:45 ` Ed Tomlinson
2002-07-23 14:31 ` Steven Cole
2002-07-24 20:28 ` Steven Cole
2002-07-24 21:02 ` Steven Cole
-- strict thread matches above, loose matches on Subject: below --
2002-07-25 0:12 Ed Tomlinson
2002-07-25 12:00 ` Craig Kulesa
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=200207222021.51600.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=ckulesa@as.arizona.edu \
--cc=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=scole@lanl.gov \
/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