fwts: maxreadreq should explain why a low setting is bad

Bug #859651 reported by Colin Ian King on 2011-09-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fwts (Ubuntu)
Colin Ian King

Bug Description

The fwts maxreadreq test gives rather too little information regarding why a low MaxReadReq PCI setting is bad. It should contain a message such as:

"The MaxReadRequest size is set too low and will affect performance. It will provide excellent bus sharing at the cost of bus data transfer rates. Although not a critical issue, it may be worth considering setting the MaxReadRequest size to 256 or 512 to increase throughput on the PCI Express bus. Some drivers (for example the Brocade Fibre Channel driver) allow one to override the firmware settings. Perhaps this is a BIOS configuration setting that can be modified, if so, it may be worth increasing it."

Changed in fwts (Ubuntu):
status: New → In Progress
importance: Undecided → Low
assignee: nobody → Colin King (colin-king)
Colin Ian King (colin-king) wrote :

Committed with commit 7eb510a605587601e94a4db2bb1a8129cd3b83d9, will be available in V0.24.02

Changed in fwts (Ubuntu):
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package fwts - 0.23.25

fwts (0.23.25) oneiric; urgency=low

  * acpi: checksum: output correct checksum value (LP: #869018)
  * framework: -T option should be -t, (LP: #868226)

fwts (0.23.24) oneiric; urgency=low

  * acpi: method: relax _BIF, _BIX tests.
  * acpi: method: Check _BST charging + discharging more thoroughly (LP: #862153)
  * acpi: acpitables: fix spurious advice infomation (LP: #862170)
  * pci: maxreadreq: add more helpful advice (LP: #859651)
 -- Colin King <email address hidden> Thu, 6 Oct 2011 15:11:00 +0100

Changed in fwts (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers