From: Matthew Wilcox <matthew@wil.cx>
To: Nick Piggin <npiggin@suse.de>
Cc: Richard Kojedzinszky <krichy@tvnetwork.hu>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: minix/ext2 + rd problem
Date: Wed, 15 Oct 2008 13:22:54 -0600 [thread overview]
Message-ID: <20081015192254.GL15064@parisc-linux.org> (raw)
In-Reply-To: <20081015143425.GA2316@wotan.suse.de>
On Wed, Oct 15, 2008 at 04:34:25PM +0200, Nick Piggin wrote:
> You can flush and invalidate the blockdev with the --flushbufs argument
> to blockdev command. However you can't use this with ramdisk devices:
> someone thought it would be a good idea to save on precious ioctl space
> and implemented totally different semantics on that device with the
> same ioctl (it throws away the underlying data as well as the cache).
What happens if we declare that a bug and fix it (and add a new ioctl to
actually throw away the data ... oh, wait, we have one, it's BLKDISCARD)?
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-10-15 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.1.10.0810141631130.30331@krichy.tvnetwork.hu>
[not found] ` <20081015041644.GA24613@wotan.suse.de>
[not found] ` <alpine.DEB.1.10.0810150943350.3259@krichy.tvnetwork.hu>
2008-10-15 14:05 ` minix/ext2 + rd problem Nick Piggin
2008-10-15 14:10 ` Richard Kojedzinszky
2008-10-15 14:34 ` Nick Piggin
2008-10-15 19:22 ` Matthew Wilcox [this message]
2008-10-16 3:48 ` Nick Piggin
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=20081015192254.GL15064@parisc-linux.org \
--to=matthew@wil.cx \
--cc=krichy@tvnetwork.hu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).