lkml.org 
[lkml]   [2002]   [Dec]   [7]   [last100]   RSS Feed
Views: [more markup]   [less markup]   [headers]   [forward]  
 
Messages in this thread
/
DateFri, 06 Dec 2002 22:45:00 -0800
FromAndrew Morton <>
SubjectRe: [BENCHMARK] max bomb segment tuning with read latency 2 patchin contest
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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:31    [W:0.746 / U:0.500 seconds]
©2003-2008 Jasper Spaans