From: Jens Axboe <axboe@suse.de>
To: Nix <nix@esperi.org.uk>
Cc: Ariel <askernel2615@dsgml.com>,
Jamie Heilman <jamie@audible.transient.net>,
Chase Venters <chase.venters@clientec.com>,
Arjan van de Ven <arjan@infradead.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: memory leak in scsi_cmd_cache 2.6.15
Date: Sat, 28 Jan 2006 20:27:14 +0100 [thread overview]
Message-ID: <20060128192714.GI9750@suse.de> (raw)
In-Reply-To: <87ek2td4i9.fsf@amaterasu.srvr.nix>
On Fri, Jan 27 2006, Nix wrote:
> On 26 Jan 2006, Ariel noted:
> > Is this good or bad? I'm guessing it means it's still leaking. So it's
> > really starting to look like ata_piix is the problem. But we need someone
> > who has the leak to remove that and see if it helps. I can't, since my
> > drives are connected to it.
>
> FWIW, a bit of negative-confirmatory evidence: I have a sym53c875
> and non-SATA IDE drive on this 2.6.15.1, and there is no leak,
> nor was there in 2.6.15:
>
> 11 11 100% 0.34K 1 11 4K scsi_cmd_cache
It's not a bad data point, it just confirms that setting ->ordered_flush
to 0 in the SATA drivers will fix the leak. So really, it's as expected.
So far apparently nobody tried it, suggested it twice.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-28 19:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 2:13 memory leak in scsi_cmd_cache 2.6.15 Ariel
2006-01-22 6:58 ` Andrew Morton
2006-01-22 18:18 ` Ariel
2006-01-22 8:16 ` Arjan van de Ven
2006-01-22 8:20 ` Arjan van de Ven
2006-01-22 18:51 ` Ariel
2006-01-22 19:07 ` Arjan van de Ven
2006-01-22 19:16 ` Chase Venters
2006-01-22 19:24 ` Arjan van de Ven
2006-01-22 19:46 ` Chase Venters
2006-01-23 2:19 ` Ariel
2006-01-22 19:24 ` Chase Venters
2006-01-23 0:58 ` Jamie Heilman
2006-01-23 2:14 ` Ariel
2006-01-23 6:18 ` Arjan van de Ven
2006-01-23 6:28 ` Chase Venters
2006-01-23 6:46 ` Ariel
2006-01-23 7:25 ` Jamie Heilman
2006-01-23 8:33 ` Jens Axboe
2006-01-27 11:28 ` Jamie Heilman
2006-01-28 19:27 ` Jens Axboe
2006-01-26 18:12 ` Ariel
2006-01-27 16:23 ` Nix
2006-01-28 19:27 ` Jens Axboe [this message]
2006-01-28 19:46 ` Chase Venters
2006-01-28 21:29 ` Jens Axboe
2006-01-29 15:50 ` Pasi Kärkkäinen
2006-01-29 16:38 ` James Bottomley
2006-01-29 17:10 ` Pasi Kärkkäinen
2006-01-29 19:57 ` Jens Axboe
2006-01-29 19:57 ` Jens Axboe
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=20060128192714.GI9750@suse.de \
--to=axboe@suse.de \
--cc=arjan@infradead.org \
--cc=askernel2615@dsgml.com \
--cc=chase.venters@clientec.com \
--cc=jamie@audible.transient.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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.