All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charu Chaubal <Charu.Chaubal@Eng.Sun.COM>
To: ultralinux@vger.kernel.org
Subject: Solaris tmpfs vs. Linux RAMdisk
Date: Tue, 13 Apr 1999 23:35:47 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-92405694308530@msgid-missing> (raw)

How comparable are tmpfs on Solaris and /dev/ram on Linux?

do they essentially provide the same thing?  are there any
particular ways in which they should be set up (flags, parameters, etc)?

if all I am looking for is a really really fast filesystem on each (for files 
that aren't huge), will each behave more or less like that?

or is there a better equivalent on Linux?

==================================Charu Chaubal				charu.chaubal@eng.sun.com    
Performance Engineer			650-786-7672              tel
Performance/Benchmarks			650-786-7323              fax
SMCC Desktop Engineering		650-786-7281              lab
==================================

             reply	other threads:[~1999-04-13 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-13 23:35 Charu Chaubal [this message]
     [not found] <19990414141937.A23591@avanticorp.com>
1999-04-15 22:14 ` Solaris tmpfs vs. Linux RAMdisk Dax Kelson

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=marc-linux-ultrasparc-92405694308530@msgid-missing \
    --to=charu.chaubal@eng.sun.com \
    --cc=ultralinux@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 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.