From: David Woodhouse <dwmw2@infradead.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
parsley@roanoke.edu, linux-kernel@vger.kernel.org
Subject: Re: Patch (repost): cramfs memory corruption fix
Date: Mon, 08 Jan 2001 13:11:56 +0000 [thread overview]
Message-ID: <23514.978959516@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10101071938540.28661-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10101071938540.28661-100000@penguin.transmeta.com>
torvalds@transmeta.com said:
> Also, if you care about memory usage, you're likely to be much better
> off using ramfs rather than something like "ext2 on ramdisk". You
> won't get the double buffering.
That'll be even more useful once we can completely configure out all
support for block devices too.
--
dwmw2
-
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/
next prev parent reply other threads:[~2001-01-08 13:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 6:41 Patch (repost): cramfs memory corruption fix Adam J. Richter
2001-01-07 13:53 ` Alan Cox
2001-01-07 19:26 ` Linus Torvalds
2001-01-07 19:42 ` Alan Cox
2001-01-07 19:56 ` Linus Torvalds
2001-01-07 21:11 ` Rik van Riel
2001-01-07 21:20 ` Alan Cox
2001-01-08 6:56 ` Eric W. Biederman
2001-01-07 21:54 ` Chris Wedgwood
2001-01-08 13:37 ` Christoph Rohland
2001-01-08 14:19 ` Christoph Hellwig
2001-01-08 14:43 ` Christoph Rohland
2001-01-08 14:42 ` Alan Cox
2001-01-08 14:49 ` Christoph Rohland
2001-01-07 20:39 ` David L. Parsley
2001-01-08 18:27 ` Linus Torvalds
2001-01-08 3:46 ` Linus Torvalds
2001-01-08 13:11 ` David Woodhouse [this message]
2001-01-08 12:30 ` Shane Nay
2001-01-08 14:34 ` David Woodhouse
2001-01-10 23:30 ` [PATCH] one-liner fix for bforget() honoring BH_Protected; was: " David L. Parsley
2001-01-11 4:23 ` Linus Torvalds
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=23514.978959516@redhat.com \
--to=dwmw2@infradead.org \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parsley@roanoke.edu \
--cc=torvalds@transmeta.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 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.