From: Theodore Ts'o <tytso@mit.edu>
To: Subranshu Patel <spatel.ml@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: fsck memory usage
Date: Wed, 1 May 2013 00:09:19 -0400 [thread overview]
Message-ID: <20130501040919.GA22839@thunk.org> (raw)
In-Reply-To: <CAEUQceh8oX9TsOR-rtn44QtegGSGH_+QHm9GPcoVPqHGJMhWHw@mail.gmail.com>
On Wed, May 01, 2013 at 08:12:14AM +0530, Subranshu Patel wrote:
>
> I used the sar command for tracking memory usage. The total memory
> usage reported by sar command is around 8GB, but it includes the
> buffer and cache memory.
>
> memused = 8GB
>
> buffer = 6.7GB
>
> cache = negligible (some MBs)
>
> So I think the effective memory usage will be 1.3GB (8 - 6.7). So the
> memory reported under buffer and cache is available for use (if any
> other process requires it). Please correct my understanding.
Yes, in general this is true. I'm curious why you are you don't just
use /usr/bin/time, though.
- Ted
next prev parent reply other threads:[~2013-05-01 4:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 15:10 fsck memory usage Subranshu Patel
2013-04-17 23:07 ` Theodore Ts'o
2013-04-18 18:34 ` Andreas Dilger
2013-05-01 2:42 ` Subranshu Patel
2013-05-01 4:09 ` Theodore Ts'o [this message]
2013-05-06 1:27 ` Andreas Dilger
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=20130501040919.GA22839@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=spatel.ml@gmail.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.