From: marcus hall <marcus@tuells.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Block device swamping disk cache
Date: Wed, 12 May 2004 07:33:29 -0600 [thread overview]
Message-ID: <20040512133329.GA20030@bastille.tuells.org> (raw)
In-Reply-To: <20040511172643.36df7c94.akpm@osdl.org>
On Tue, May 11, 2004 at 05:26:43PM -0700, Andrew Morton wrote:
> no, sorry, it'll still happen. I haven't fixed the ramdisk driver yet.
>
> The problem is that ->memory_backed means both "doesn't contribute
> to dirty memory" and also "doesn't need writeback".
>
> These concepts need to be split apart for the ramdisk driver. I'll do it
> for 2.6.7, promise.
Well, I believe that the inodes that are marked as memory_backed are
for the ramdisk, and that isn't really a problem. The block device
that I am writing to is a compact flash, so it's going through the ide-disk
device. I do not see this inode show up on any superblock's dirty queue
(since it doesn't appear that mark_inode_dirty() is being called for
it). So the question I am asking is, what strategy is *supposed* to be
in place to flush the blocks out? (Or is this a hole that isn't plugged?)
Marcus Hall
marcus@tuells.org
next prev parent reply other threads:[~2004-05-12 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 19:11 marcus hall
2004-05-11 19:19 ` Christoph Hellwig
2004-05-11 19:48 ` marcus hall
2004-05-12 0:26 ` Andrew Morton
2004-05-12 13:33 ` marcus hall [this message]
2004-05-13 0:20 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-05-07 23:23 marcus hall
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=20040512133329.GA20030@bastille.tuells.org \
--to=marcus@tuells.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®