public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Lukasz Trabinski <lukasz@wsisiz.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Two suggestions (loop and owner's of linux tree)
Date: Thu, 25 Oct 2001 11:27:52 +0200	[thread overview]
Message-ID: <20011025112752.A4795@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0110241605020.12884-100000@oceanic.wsisiz.edu.pl>
In-Reply-To: <Pine.LNX.4.33.0110241605020.12884-100000@oceanic.wsisiz.edu.pl>

On Wed, Oct 24 2001, Lukasz Trabinski wrote:
> Hello
> 
> I would like to suggest to change max_loop from 8 to 16 or more if it
> possible.
> 
> --- linux.org/drivers/block/loop.c      Wed Oct 24 15:23:11 2001
> +++ linux/drivers/block/loop.c  Wed Oct 24 15:24:52 2001
> @@ -75,7 +75,7 @@
>  
>  #define MAJOR_NR LOOP_MAJOR
>  
> -static int max_loop = 8;
> +static int max_loop = 16;
>  static struct loop_device *loop_dev;
>  static int *loop_sizes;
>  static int *loop_blksizes;

You just bumped loop memory usage by 24000 bytes on my system with
something that can be handled with a boot parameter. I'd rather see a
max_loop = 4 or something patch instead...

-- 
Jens Axboe


  parent reply	other threads:[~2001-10-25  9:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-24 14:13 Two suggestions (loop and owner's of linux tree) Lukasz Trabinski
2001-10-24 14:21 ` Dumitru Ciobarcianu
2001-10-24 14:38   ` Lukasz Trabinski
2001-10-24 14:48     ` Miquel van Smoorenburg
2001-10-24 14:57     ` James Sutherland
2001-10-24 15:04       ` Lukasz Trabinski
2001-10-25  9:27 ` Jens Axboe [this message]
2001-10-25  9:52   ` Asus CUV-266-D vs Intel NIC Dead2
2001-10-25 10:18     ` Asus CUV-266-D vs Intel NIC (also MSI-6321) Dead2
2001-10-25 10:39       ` Dead2

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=20011025112752.A4795@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz@wsisiz.edu.pl \
    /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