From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Feedback for fastselect and one-copy-pipe
Date: Mon, 12 Mar 2001 17:58:34 +0100 [thread overview]
Message-ID: <20010312175834.D878@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20010312151548.B878@nightmaster.csn.tu-chemnitz.de> <Pine.LNX.4.33.0103121710030.927-100000@mikeg.weiden.de>
In-Reply-To: <Pine.LNX.4.33.0103121710030.927-100000@mikeg.weiden.de>; from mikeg@wen-online.de on Mon, Mar 12, 2001 at 05:20:12PM +0100
On Mon, Mar 12, 2001 at 05:20:12PM +0100, Mike Galbraith wrote:
> I just happen to have a 2.4.2 IKD patch sitting here, and therein
> sits Ingo's memory leak detector... poor thing is bored to tears 8)
Could to point me to mingos[1] memleak-detector? I need to know,
whats going on here.
I have had a load of 10 today, a much to busy disk and a full
swap.
I killed X and killed -9 netscape several times and waited a
while. Things didn't settle down until reboot.
So I definitly would like to try all that doesn't corrupt my fs ;-)
Regards
Ingo Oeser
[1] If people wonder, why I ask about "my own" patch: Mike means
Ingo *Molnar* (nickname mingo), which is NOT me (nickname ioe).
I'm NOT going to change my name because of this, ok? ;-)
--
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< been there and had much fun >>>>>>>>>>>>
next prev parent reply other threads:[~2001-03-12 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 14:15 Feedback for fastselect and one-copy-pipe Ingo Oeser
2001-03-12 16:20 ` Mike Galbraith
2001-03-12 16:58 ` Ingo Oeser [this message]
2001-03-12 17:29 ` Mike Galbraith
2001-03-12 16:42 ` Manfred Spraul
2001-03-12 18:12 ` kuznet
2001-03-12 18:42 ` Manfred Spraul
2001-03-12 19:40 ` kuznet
2001-03-12 20:05 ` Manfred Spraul
2001-03-12 20:08 ` kuznet
2001-03-12 20:28 ` Manfred Spraul
2001-03-12 20:31 ` kuznet
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=20010312175834.D878@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
/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.