From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andreas Dilger <adilger@sun.com>
Cc: Michal Simek <michal.simek@petalogix.com>,
Nate Straz <nate-ltp@refried.org>,
subrata@linux.vnet.ibm.com, ltp-list@lists.sourceforge.net,
John Williams <john.williams@petalogix.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [LTP] statvfs -> f_bavail
Date: Tue, 21 Apr 2009 01:47:57 +0100 [thread overview]
Message-ID: <20090421004757.GC8633@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20090421003847.GO3209@webber.adilger.int>
On Mon, Apr 20, 2009 at 06:38:47PM -0600, Andreas Dilger wrote:
> On Apr 21, 2009 01:25 +0100, Al Viro wrote:
> > a) ramfs has no such thing as "amount of available space", simply
> > because it has no limit on total size occupied.
>
> Well, except the amount of RAM in the system, which would be a reasonable
> value to use.
You are welcome to provide an analysis of differences between the moments
when OOM hits root and non-root resp. if they keep allocating there...
next prev parent reply other threads:[~2009-04-21 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49E759FB.70103@petalogix.com>
[not found] ` <49E847FB.1030801@petalogix.com>
[not found] ` <20090417173107.GA3590@refried.org>
2009-04-20 6:16 ` [LTP] statvfs -> f_bavail Michal Simek
2009-04-20 6:26 ` Al Viro
2009-04-20 6:42 ` Michal Simek
[not found] ` <49EC1945.1000805-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
2009-04-20 22:59 ` Nate Straz
2009-04-21 0:25 ` [LTP] " Al Viro
2009-04-21 0:38 ` Andreas Dilger
2009-04-21 0:47 ` Al Viro [this message]
2009-04-21 8:45 ` Michal Simek
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=20090421004757.GC8633@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=adilger@sun.com \
--cc=john.williams@petalogix.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=michal.simek@petalogix.com \
--cc=nate-ltp@refried.org \
--cc=subrata@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).