From: Tommy Reynolds <Tommy.Reynolds@MegaCoder.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Gigantic memory leak in linux-2.6.[789]!
Date: Sun, 24 Oct 2004 11:04:10 -0500 [thread overview]
Message-ID: <20041024110410.0cf3f80e.Tommy.Reynolds@MegaCoder.com> (raw)
In-Reply-To: <clgc6m$u72$1@gatekeeper.tmr.com>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
Uttered Bill Davidsen <davidsen@tmr.com>, spake thus:
> With all the work Nick, Ingo,Con and others are putting into latency and
> responsiveness, I don't understand why anyone thinks this is desirable
> behavior. The idle loop is the perfect place to perform things like
> this, to convert non-productive cycles into performing tasks which will
> directly improve response and performance when the task MUST be done.
Bill, with respect,
The idle loop is, by definition, the place to go when there is
nothing else to do. Scrubbing memory is, by definition, not
"nothing", so leave the idle loop alone.
That's why God, or maybe it was Linus, invented kernel threads.
Cheers!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-24 16:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 14:13 Gigantic memory leak in linux-2.6.[789]! Kristian Sørensen
2004-10-22 14:32 ` Kasper Sandberg
2004-10-22 15:07 ` Richard B. Johnson
2004-10-22 15:50 ` Kristian Sørensen
2004-10-22 16:12 ` Richard B. Johnson
2004-10-22 19:24 ` Kristian Sørensen
2004-10-22 19:20 ` Richard B. Johnson
2004-10-22 19:33 ` Chris Friesen
2004-10-22 16:15 ` Gene Heskett
2004-10-22 16:28 ` Andre Tomt
2004-10-22 16:32 ` Chris Friesen
2004-10-23 0:51 ` David Lang
2004-10-24 14:14 ` Bill Davidsen
2004-10-24 16:04 ` Tommy Reynolds [this message]
2004-10-25 22:11 ` Bill Davidsen
2004-10-25 22:47 ` David Lang
2004-10-23 1:44 ` Bernd Eckenfels
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=20041024110410.0cf3f80e.Tommy.Reynolds@MegaCoder.com \
--to=tommy.reynolds@megacoder.com \
--cc=davidsen@tmr.com \
--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 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.