All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: tglx@linutronix.de
Cc: michal.k.k.piotrowski@gmail.com,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.20-rc6 ramdisk problem
Date: Wed, 31 Jan 2007 18:14:20 -0600	[thread overview]
Message-ID: <45C130DC.90905@shaw.ca> (raw)
In-Reply-To: <1170288386.29240.234.camel@localhost.localdomain>

Thomas Gleixner wrote:
> On Wed, 2007-01-31 at 17:54 -0600, Robert Hancock wrote:
>> I'm not sure if there's an inherent max ramdisk size limit, however I 
>> should point out that in most cases, using a tmpfs or ramfs file system 
>> is better than old-style ramdisks. Those filesystems return unused 
>> memory to the kernel (ramdisks statically allocate the entire space) and 
>> also avoid the filesystem overhead of ramdisks (the files are mapped 
>> into pagecache directly).
> 
> This is not a question of what's better or not. 
> 
> Michal stepped into a real life problem:
> 
> 1. ramdisk gets created in the first place w/o problems
> 2. formatting the same ramdisk succeeds
> 3. trying to use it fails
> 
> So either #1 or #2 should have failed in the first place. Failing in #3
> is definitely a BUG in #1 or #2.
> 
> How does your advise help to fix that BUG ? Ignoring it by using
> something else ?

Yes, there is likely a bug here of some sort. However, that doesn't 
change the fact that ramdisks are sub-optimal for most uses.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/



  reply	other threads:[~2007-02-01  0:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.nr9vhGrVS5zmSNQEe1vQ/Ktii9w@ifi.uio.no>
2007-01-31 23:54 ` 2.6.20-rc6 ramdisk problem Robert Hancock
2007-02-01  0:06   ` Thomas Gleixner
2007-02-01  0:14     ` Robert Hancock [this message]
2007-02-01  0:40       ` Thomas Gleixner
2007-01-31 13:55 Michal Piotrowski

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=45C130DC.90905@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=tglx@linutronix.de \
    /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.