From: marcus hall <marcus@tuells.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Block device swamping disk cache
Date: Tue, 11 May 2004 13:48:53 -0600 [thread overview]
Message-ID: <20040511194853.GA16216@bastille.tuells.org> (raw)
In-Reply-To: <20040511201936.A19384@infradead.org>
On Tue, May 11, 2004 at 08:19:36PM +0100, Christoph Hellwig wrote:
> > I am running an arm version of the 2.5.59 kernel.
>
> I don't think anyone here still remembers stoneage-aera kernels.
>
> You're better off trying to reproduce it with 2.6.6 I guess.
Well, when we started the project, the 2.5.59 base was the most current.
Since then, there hasn't been time to try to update all of the drivers to
the 2.6 kernel. I would like to eventually get there, but at this point
it's an unfunded mandate.
So, my question is just in general terms, what is supposed to occur to flush
blocks out to a block device? Is the inode supposed to be marked as dirty
and queued on the superblock containing the block device file (sort of what
I expected to be seeing), or is there some other method? I can transpose
between the 2.6 and 2.5 kernels enough to try to see what isn't happening,
unless the strategy has changed in the 2.6 kernel..
Marcus Hall
marcus@tuells.org
next prev parent reply other threads:[~2004-05-11 19:47 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 [this message]
2004-05-12 0:26 ` Andrew Morton
2004-05-12 13:33 ` marcus hall
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=20040511194853.GA16216@bastille.tuells.org \
--to=marcus@tuells.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®