From: Nick Piggin <npiggin@suse.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Richard Kojedzinszky <krichy@tvnetwork.hu>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: minix/ext2 + rd problem
Date: Thu, 16 Oct 2008 05:48:12 +0200 [thread overview]
Message-ID: <20081016034812.GA10371@wotan.suse.de> (raw)
In-Reply-To: <20081015192254.GL15064@parisc-linux.org>
On Wed, Oct 15, 2008 at 01:22:54PM -0600, Matthew Wilcox wrote:
> 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)?
Well... that's a good point. We probably could, because the worst someone
will see is their backing store memory does not get freed. It won't munch
someone's data.
I'd love to do this, OTOH we've had the old behaviour, apparently documented
and used by someone at some point, for a long time :(
prev parent reply other threads:[~2008-10-16 3:48 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
2008-10-16 3:48 ` Nick Piggin [this message]
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=20081016034812.GA10371@wotan.suse.de \
--to=npiggin@suse.de \
--cc=krichy@tvnetwork.hu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
/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).