Skip to contentSkip to conversation

cfq: depth 4 reached, tagging now on

DISCUSSION Lee Revell 2 participants 3 messages Feb 19, 2005 – Feb 22, 2005

lore
Share & tools
lore

Lee Revell

author
#0 lore raw

Starting around 2.6.11-rc4 I get this printk during the boot process after kjournald starts, and again if I stress the filesystem.

cfq: depth 4 reached, tagging now on

Is this printk intentional? I am sure users will wonder about it, especially because (presumably) cfq turns tagging off at some point in between, and doesn't say anything about it.

Lee

#1 lore raw
Quoted 8 lines · Lee Revell

Starting around 2.6.11-rc4 I get this printk during the boot process after kjournald starts, and again if I stress the filesystem.

cfq: depth 4 reached, tagging now on

Is this printk intentional? I am sure users will wonder about it, especially because (presumably) cfq turns tagging off at some point in between, and doesn't say anything about it.

It is intentional, but could be supressed. But I'm wondering if the accounting change introduced a bug - what hardware are you using cfq on (ie does it actually do tagged command queueing, is it SCSI?)?

It's a one-time message. CFQ starts out assuming the drive doesn't do TCQ, if the driver depth goes beyond a defined limit (4), it will assume that the hardware can do tagged queueing and change its internal accounting accordingly. The setting stays that way, it's not a transitional state.

Signature · 1 line
Jens Axboe
author
#2 lore raw
Quoted 6 lines · Jens Axboe
Quoted 5 lines · Lee Revell

Starting around 2.6.11-rc4 I get this printk during the boot process after kjournald starts, and again if I stress the filesystem.

cfq: depth 4 reached, tagging now on

Quoted 8 lines
Quoted 3 lines

Is this printk intentional? I am sure users will wonder about it, especially because (presumably) cfq turns tagging off at some point in between, and doesn't say anything about it.

It is intentional, but could be supressed. But I'm wondering if the accounting change introduced a bug - what hardware are you using cfq on (ie does it actually do tagged command queueing, is it SCSI?)?

Yes, this is an all SCSI system using the aic7xxx driver.

Quoted 6 lines

It's a one-time message. CFQ starts out assuming the drive doesn't do TCQ, if the driver depth goes beyond a defined limit (4), it will assume that the hardware can do tagged queueing and change its internal accounting accordingly. The setting stays that way, it's not a transitional state.

OK. Then the multiple messages were CFQ enabling TCQ for the different drives.

Lee