From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: karl.vogel@seagha.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8.1+patches: Still a memory leak with cdrecord
Date: Fri, 27 Aug 2004 16:33:27 +0200 [thread overview]
Message-ID: <412F4637.8080901@bio.ifi.lmu.de> (raw)
In-Reply-To: <Xns9552A4ACE4078gmovkeb@80.91.224.252>
Karl Vogel wrote:
>
> I'm not sure, but this sounds a bit similar to a problem I am seeing. Are
> you by any chance using the CFQ scheduler?! (elevator=cfq) If so, give
> elevator=as or elevator=deadline a go.
I've no idea what the CFQ scheduler is :-) I'm not using anything like that
on the kernel append line, so if it's not standard, then no, I'm likely
not using it...
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
next prev parent reply other threads:[~2004-08-27 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 12:23 2.6.8.1+patches: Still a memory leak with cdrecord Frank Steiner
2004-08-27 14:09 ` Karl Vogel
2004-08-27 14:33 ` Frank Steiner [this message]
2004-08-27 15:41 ` Karl Vogel
2004-08-30 8:57 ` Frank Steiner
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=412F4637.8080901@bio.ifi.lmu.de \
--to=fsteiner-mail@bio.ifi.lmu.de \
--cc=karl.vogel@seagha.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox