From: David Woodhouse <dwmw2@infradead.org>
To: Simon Munton <Simon.Munton@m4data.co.uk>
Cc: "JFFS (E-mail)" <jffs-dev@axis.com>, "MTD (E-mail)" <mtd@infradead.org>
Subject: Re: Endless garbage collection
Date: Tue, 23 Jan 2001 16:06:24 +0000 [thread overview]
Message-ID: <5100.980265984@redhat.com> (raw)
In-Reply-To: <52AF3CB987C7D41183CD0090271F67C301C7CE@m4eng.m4data.co.uk>
Simon.Munton@m4data.co.uk said:
> Perhaps the test for too much RAM being used in thread_should_wake()
> ought to take the number of files into account? ie should it be:
Probably something along the lines of what you suggested. I think we should
probably put it _after_ the check for dirty_size < sector_size too,
until/unless we can be 100% sure that it'll never cause endless GC.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-01-23 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 15:59 Endless garbage collection Simon Munton
2001-01-23 16:06 ` David Woodhouse [this message]
2001-01-23 16:20 ` Martin Gadbois
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=5100.980265984@redhat.com \
--to=dwmw2@infradead.org \
--cc=Simon.Munton@m4data.co.uk \
--cc=jffs-dev@axis.com \
--cc=mtd@infradead.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 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.