From: Dave Pifke <dave@birthdayalarm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about buffer usage
Date: Wed, 19 Oct 2005 16:23:09 -0700 [thread overview]
Message-ID: <4356D55D.5060303@birthdayalarm.com> (raw)
In-Reply-To: <20051019154940.55f18786.akpm@osdl.org>
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.
--
Dave Pifke, dave@bebo.com
Sr. System Administrator, www.bebo.com
next prev parent reply other threads:[~2005-10-19 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 21:59 Question about buffer usage Dave Pifke
2005-10-19 22:49 ` Andrew Morton
2005-10-19 23:23 ` Dave Pifke [this message]
2005-10-20 2:45 ` Dave Kleikamp
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=4356D55D.5060303@birthdayalarm.com \
--to=dave@birthdayalarm.com \
--cc=akpm@osdl.org \
--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.