no luck with max_sectors_kb (Re: voluntary-preempt-2.6.8-rc2-J4)

[Rudo Thomas]

> > Changes since -J3:
> > 
> >  - make block device max_sectors sysfs tunable. There's a new entry
> >    /sys/block/*/queue/max_sectors_kb which stores the current max 
> >    request size in KB. You can write it to change the size.
> > 
> > [...]
>
> i've refined the patch (new version attached below): drivers use
> blk_queue_max_sectors() to set the maximum # of sectors that the driver
> or hw can handle.
> 
> so i've introduced a new queue entry called max_hw_sectors, and the new
> /sys entry listens to this maximum and only updates max_sectors. This
> entry is also exported to /sys as a readonly entry. (so that users can
> see the maximum the driver supports.)

Hi there.

I do not seem to have success with tuning the max_sectors_kb value.

After setting it to 32 (the hw max is 128), userland programs fail with I/O
errors. Setting it back to 128 gets it back to working, sort of. The errors
probably get bufferred somewhere.

During the "bad" setting (32), messages like this one show up in kernel log.

bio too big device hda3 (104 > 64)

I am using J7 voluntary_preemption patch (set at 2:1), cfq io scheduler,
via82cxxx IDE driver. I will gladly provide further details.

Rudo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/