linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Ariel <askernel2615@dsgml.com>,
	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: Mon, 23 Jan 2006 09:33:47 +0100	[thread overview]
Message-ID: <20060123083347.GA12773@suse.de> (raw)
In-Reply-To: <20060123072556.GC15490@fifty-fifty.audible.transient.net>

On Sun, Jan 22 2006, Jamie Heilman wrote:
> Ariel wrote:
> > I'm on ICH5, but also Sil3112 and HighPoint 372N.
> > 
> > Jamie has ICH6 and Sil3112.
> > 
> > ata_piix seems like it's in common for all, but this is not a lot of 
> > systems, so it could just be a coincidence and the problem caused by 
> > something that's not chipset specific.
> 
> Hmm.  I just moved my sata_sil stuff out of the way and rebooted:
> 
> $ uptime; grep scsi_cmd_cache /proc/slabinfo
>  23:22:16 up 4 min,  1 user,  load average: 0.00, 0.03, 0.00
> scsi_cmd_cache      1200   1200    384   10    1 : tunables   54   27   8 : slabdata    120    120      0
> 
> My other workstation also runs 2.6.15.1 but uses sata_nv and doesn't
> exhibit the problem.

The SATA low level driver is very unlikely to play a role in this. But
you are both using md (raid1 to be specific) on top of scsi, I'd say
that's the best clue. I'd very much doubt the nvidia module as well.

-- 
Jens Axboe


  reply	other threads:[~2006-01-23  8:31 UTC|newest]

Thread overview: 30+ 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 [this message]
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
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

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=20060123083347.GA12773@suse.de \
    --to=axboe@suse.de \
    --cc=arjan@infradead.org \
    --cc=askernel2615@dsgml.com \
    --cc=chase.venters@clientec.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).