All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: GrandMasterLee <masterlee@digitalroadkill.net>
Cc: Con Kolivas <conman@kolivas.net>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] max bomb segment tuning with read latency 2 patchin   contest
Date: Fri, 06 Dec 2002 22:45:00 -0800	[thread overview]
Message-ID: <3DF198EC.CDAB69D1@digeo.com> (raw)
In-Reply-To: 1039242017.2855.26.camel@localhost

GrandMasterLee wrote:
> 
> ...
> One interesting thing about my current setup, with all scsi or FC disks,
> is that bomb never displays > 0.
> Example:
> 
> elvtune /dev/sdn yields:
> 
> /dev/sdn elevator ID            17
>         read_latency:           8192
>         write_latency:          16384
>         max_bomb_segments:      0
> 
> elvtune -b 6 /dev/sdn yields:
> 
> /dev/sdn elevator ID            17
>         read_latency:           8192
>         write_latency:          16384
>         max_bomb_segments:      0
> 
> Is it because I just do volume management at the hardware level and use
> whole disks? Or is that something else?

You need a patched kernel.  max_bomb_segments is some old thing
which isn't implemented any more.  But I reused it for something
completely different in the patch which Con is testing.  So I
wouldn't have to futz around with patching userspace apps.

  reply	other threads:[~2002-12-07  6:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-07  5:20 [BENCHMARK] max bomb segment tuning with read latency 2 patch in contest Con Kolivas
2002-12-07  5:55 ` Andrew Morton
2002-12-07  6:09   ` Con Kolivas
2002-12-07  6:14     ` Andrew Morton
2002-12-07  6:15   ` GrandMasterLee
2002-12-07  6:20   ` GrandMasterLee
2002-12-07  6:45     ` Andrew Morton [this message]
2002-12-07 13:29 ` Con Kolivas
2002-12-10 10:50 ` Miquel van Smoorenburg
2002-12-10 10:55   ` Marc-Christian Petersen

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=3DF198EC.CDAB69D1@digeo.com \
    --to=akpm@digeo.com \
    --cc=conman@kolivas.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masterlee@digitalroadkill.net \
    /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.