public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: dougg@torque.net
Cc: pbadari@us.ibm.com, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: Re: [patch for playing] 2.5.65 patch to support > 256 disks
Date: Sat, 22 Mar 2003 04:05:50 -0800	[thread overview]
Message-ID: <20030322040550.0b8baeec.akpm@digeo.com> (raw)
In-Reply-To: <3E7C4D05.2030500@torque.net>

Douglas Gilbert <dougg@torque.net> wrote:
>
> Andrew Morton wrote:
> > Douglas Gilbert <dougg@torque.net> wrote:
> > 
> >>>Slab:           464364 kB
> >>
> > 
> > It's all in slab.
> > 
> > 
> >>I did notice a rather large growth of nodes
> >>in sysfs. For 84 added scsi_debug pseudo disks the number
> >>of sysfs nodes went from 686 to 3347.
> >>
> >>Does anybody know what is the per node memory cost of sysfs?
> > 
> > 
> > Let's see all of /pro/slabinfo please.
> 
> Andrew,
> Attachments are /proc/slabinfo pre and post:
>   $ modprobe scsi_debug add_host=42 num_devs=2
> which adds 84 pseudo disks.
> 

OK, thanks.  So with 48 disks you've lost five megabytes to blkdev_requests
and deadline_drq objects.  With 4000 disks, you're toast.  That's enough
request structures to put 200 gigabytes of memory under I/O ;)

We need to make the request structures dymanically allocated for other
reasons (which I cannot immediately remember) but it didn't happen.  I guess
we have some motivation now.


  reply	other threads:[~2003-03-22 12:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 18:56 [patch for playing] 2.5.65 patch to support > 256 disks Badari Pulavarty
2003-03-22 11:00 ` Douglas Gilbert
2003-03-22 11:04   ` Andrew Morton
2003-03-22 11:46     ` Douglas Gilbert
2003-03-22 12:05       ` Andrew Morton [this message]
2003-03-24 21:32         ` Badari Pulavarty
2003-03-24 22:22           ` Douglas Gilbert
2003-03-24 22:54             ` Badari Pulavarty
2003-03-25  0:10           ` Andrew Morton
2003-03-24 22:57             ` Badari Pulavarty
2003-03-25 10:56         ` Jens Axboe
2003-03-25 11:23           ` Jens Axboe
2003-03-25 11:37             ` Jens Axboe
2003-03-25 11:39           ` Nick Piggin
2003-03-25 12:01             ` Jens Axboe
2003-03-25 12:12               ` Nick Piggin
2003-03-25 12:35                 ` Jens Axboe
2003-03-27  0:29                   ` Badari Pulavarty
2003-03-27  9:18                     ` Jens Axboe
2003-03-28 17:04                       ` Badari Pulavarty
2003-03-28 18:41                         ` Andries Brouwer
2003-03-29  1:39                           ` Badari Pulavarty

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=20030322040550.0b8baeec.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=axboe@suse.de \
    --cc=dougg@torque.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    /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