public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: Christoph Rohland <cr@sap.com>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
	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 07:56:28 -0600	[thread overview]
Message-ID: <m37l3yck4z.fsf@austin.jhcloos.com> (raw)
In-Reply-To: <200101132014.f0DKEJh153332@saturn.cs.uml.edu> <m3itnih3eb.fsf@linux.local>
In-Reply-To: <m3itnih3eb.fsf@linux.local>

>>>>> "Christoph" == Christoph Rohland <cr@sap.com> writes:

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

I think vmfs is the better choice.  Not to be gratuitously
incompatable with sun, but there is no guarentee linux's
implementation and sun's will be or remain compatable, so it really
doesn't hurt to choose a name which is more descriptive rather than
that used by someone else's product -- even if the other product is
widely deployed and understood.

>> I'd prefer k for ISO standard and K for base-2.  Of course m isn't
>> millibytes, but that isn't horrible.

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

Unquestionably the Right Thing.  VM is after all being measured, and
RAM is always measured in binary.  (OK, I just *know* someone will
provide a counter-example disproving that assertion -- perhaps the old
36 bit systems?  Or core?  But are there any modern counter-examples?)

-JimC
-- 
James H. Cloos, Jr.  <http://jhcloos.com/public_key>     1024D/ED7DAEA6 
<cloos@jhcloos.com>  E9E9 F828 61A4 6EA9 0F2B  63E7 997A 9F17 ED7D AEA6
-
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 13:56 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
2001-01-14 13:56         ` James H. Cloos Jr. [this message]
     [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=m37l3yck4z.fsf@austin.jhcloos.com \
    --to=cloos@jhcloos.com \
    --cc=acahalan@cs.uml.edu \
    --cc=cr@sap.com \
    --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