mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Dave Pifke <dave@birthdayalarm.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Question about buffer usage
Date: Wed, 19 Oct 2005 21:45:06 -0500	[thread overview]
Message-ID: <1129776306.10190.14.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <4356D55D.5060303@birthdayalarm.com>

On Wed, 2005-10-19 at 16:23 -0700, Dave Pifke wrote:
> Andrew Morton wrote:
> 
>  > It could be a JFS quirk - I don't know much about JFS.  It'd be 
> interesting
>  > to know if other filesystems behave in a similar manner.
> 
> I have two more machines on order, so perhaps I'll try a different 
> filesystem on them and report back if it makes a difference.
> 
>  > One thing you could do is to (re)mount the filesystems with `-o noatime'.
> 
> I probably should have mentioned that this is already the case.
> 
>  > That should release _some_ of the blockdev pagecache, but not a lot, I
>  > expect.  Maybe JFS is just metadata-intensive..
> 
> There appears to be a jfs-discussion mailing list on SourceForge; I'll 
> try asking there.

I answered this in jfs-discussion, but for curious on linux-kernel:

There was a pretty major memory leak in jfs in the 2.6.8 kernel.  This
one-line fix is in the 2.6.9 kernel.  I'm guessing that this would
explain the problem you are seeing.
http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/tglx/history.git;a=commitdiff;h=fcc1fcc376bb1fe8ed7609b07931fc5bd774943a

Thanks,
Shaggy
-- 
David Kleikamp
IBM Linux Technology Center


      reply	other threads:[~2005-10-20  2:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19 21:59 Dave Pifke
2005-10-19 22:49 ` Andrew Morton
2005-10-19 23:23   ` Dave Pifke
2005-10-20  2:45     ` Dave Kleikamp [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=1129776306.10190.14.camel@kleikamp.austin.ibm.com \
    --to=shaggy@austin.ibm.com \
    --cc=akpm@osdl.org \
    --cc=dave@birthdayalarm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®