From: Christoph Rohland <cr@sap.com>
To: "Norberto Bensa" <nbensa@yahoo.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: tmpfs?
Date: 19 Nov 2001 08:29:38 +0100 [thread overview]
Message-ID: <m3elmwjqqb.fsf@linux.local> (raw)
In-Reply-To: <003a01c16fe5$088ae9c0$0200000a@home>
In-Reply-To: <003a01c16fe5$088ae9c0$0200000a@home>
Hi Norberto,
On Sun, 18 Nov 2001, Norberto Bensa wrote:
> I've configured my kernel (2.4.13-ac8) to use tmpfs, but it seems
> that it only uses half my physical memory (64 of 128MB).
,----[ Configure.help ]
| Virtual memory file system support
| CONFIG_TMPFS
[...]
| You can set limits for the number of blocks and inodes used by the
| filesystem with the mount options "size", "nr_blocks" and
| "nr_inodes". These parameters accept a suffix k, m or g for kilo,
| mega and giga and can be changed on remount.
|
| The initial permissions of the root directory can be set with the
| mount option "mode".
`----
So the configure help gives you the answer: Use the size mount
option.
Greetings
Christoph
prev parent reply other threads:[~2001-11-19 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 3:56 tmpfs? Norberto Bensa
2001-11-18 11:00 ` tmpfs? José Luis Domingo López
2001-11-19 7:29 ` Christoph Rohland [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=m3elmwjqqb.fsf@linux.local \
--to=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbensa@yahoo.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