From: Linda Walsh <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Re: better perf and memory uage for xfs_fsr? Trivial patch against xfstools-3.16 included...
Date: Thu, 08 Nov 2012 12:30:11 -0800 [thread overview]
Message-ID: <509C1653.7050906@tlinx.org> (raw)
In-Reply-To: <509BAABF.3030608@tlinx.org>
FWIW, the benefit, probably comes from the read-file, as the written file
is written with DIRECT I/O and I can't see that it should make a difference
there.
Another thing I noted -- when xfs_fsr _exits_, ALL of the space it had used
for file cache read into memory -- gets freed - whereas before, it just stayed in
the buffer cache and didn't get released until the space was needed.
Linda Walsh wrote:
> I wondered why it lumped all this memory reclaiming and thought to try
> using
> the posix_fadvise calls in xfs_fsr to tell the kernel what data was
> unneeded
> and such...
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-11-08 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 12:51 better perf and memory uage for xfs_fsr? Trivial patch against xfstools-3.16 included Linda Walsh
2012-11-08 20:30 ` Linda Walsh [this message]
2012-11-08 21:39 ` Dave Chinner
2012-11-09 7:10 ` Linda Walsh
2012-11-09 8:16 ` Dave Chinner
2012-11-08 21:29 ` Dave Chinner
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=509C1653.7050906@tlinx.org \
--to=xfs@tlinx.org \
--cc=xfs@oss.sgi.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 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.