public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: david+validemail@kalifornia.com, linux-kernel@vger.kernel.org
Subject: Re: shmem or swapfs? was: [Patch] make shm filesystem part configurable
Date: 14 Jan 2001 10:56:08 +0100	[thread overview]
Message-ID: <m3itnih3eb.fsf@linux.local> (raw)
In-Reply-To: <200101132014.f0DKEJh153332@saturn.cs.uml.edu>
In-Reply-To: <200101132014.f0DKEJh153332@saturn.cs.uml.edu>

Hi Albert,

"Albert D. Cahalan" <acahalan@cs.uml.edu> writes:

> Admins already know what "tmpfs" means, so you should just call
> your filesystem that. I know it isn't a pretty name, but in the
> interest of reducing confusion, you should use the existing name.
> 
> Don't think of it as just "for /tmp". It is for temporary storage.
> The name is a reminder that you shouldn't store archives in tmpfs.

OK right now I see two alternatives for the name: "tmpfs" for the SUN
admins and "vmfs" for expressing what it does and to be in line with
"ramfs". Any votes?

> Again for compatibility, Sun's size option would be useful.
> 
> -o size=111222333      Size in bytes, rounded up by page size.
> -o size=111222k        Size in kilobytes (base-2 or ISO standard?)
> -o size=111m           Size in megabytes (base-2 or ISO standard?)
> 
> I'd prefer k for ISO standard and K for base-2.
> Of course m isn't millibytes, but that isn't horrible.

No, I would go for base-2 only. That's what we typically mean with K
and M in the IT world. To be case sensitive is IMHO overkill and
confusing.

Greetings
                Christoph 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-14  9:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-13 10:49 [Patch] make shm filesystem part configurable Christoph Rohland
2001-01-13 12:33 ` shmem or swapfs? was: " David Ford
2001-01-13 14:04   ` Christoph Rohland
2001-01-13 14:16     ` David Ford
2001-01-13 16:51       ` Christoph Rohland
2001-01-13 22:39         ` David Ford
2001-01-13 20:14     ` Albert D. Cahalan
2001-01-14  9:56       ` Christoph Rohland [this message]
2001-01-14 13:56         ` James H. Cloos Jr.
     [not found]         ` <20010114134457.A14486@uni-mainz.de>
2001-01-14 21:29           ` Christoph Rohland
  -- strict thread matches above, loose matches on Subject: below --
2001-01-13 20:58 Dan Kegel

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=m3itnih3eb.fsf@linux.local \
    --to=cr@sap.com \
    --cc=acahalan@cs.uml.edu \
    --cc=david+validemail@kalifornia.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox