On Wed, Feb 09, 2011 at 12:50:34PM +0100, Stephan wrote:
Reset it to a known state.
Okay.
No, but it's just wrong to apply the modes computed for the
virtual disk, to a physical disk.
When the controller operates in RAID mode, is target page 0 still the
disk page or the page for
which behavior ?
The behavior of resetting all target pages to 0.
both x86 I guess, and both with the BIOS enabled.
Both x86. Did you mean the mainboard BIOS or the MPT BIOS?
the MPT BIOS
Yes, it is enabled.
for FC, tagged queuing should also work AFAIK.
The driver needs some
On Wed, 9 Feb 2011, Stephan wrote:
probably. But this doesn't mean we can't enable tagged queuing now.
At last for FC it should just work.
The Linux driver also sais TQ is enabled on the SAS drives. As I said,
the adapter doesn´t like that for now. Maybe some queue size
parameters have to be
On Wed, Feb 09, 2011 at 09:38:02AM -0700, Michael L. Hitch wrote:
This might be the adapt-adapt_max_periph = maxq setting in
mpt_netbsd.c, if maxq is 256. The tagging done in the scsipi
layer can only deal with 256 tags. I'm not sure how that would
affect the mpt(4) driver. I did some
On Wed, 9 Feb 2011, Thor Lancelot Simon wrote:
But ciss uses ld(4), doesn't it? It's not a SCSI adapter?
It looks like a SCSI adapter, so uses sd(4).
--
Michael L. Hitchmhi...@montana.edu
Computer Consultant
Information Technology Center
Montana State University
Hi all!
At the very last this change should apply only when the controller is in
RAID mode.
But what´s the sense in simply scrubbing all mode pages on driver
initialisation?
In this case, the driver should also probably ignore the
modes set from the upper layer.
Does this have an impact to the
On Tue, Feb 08, 2011 at 03:06:41PM +0100, Stephan wrote:
Hi all!
At the very last this change should apply only when the controller is in
RAID mode.
But what´s the sense in simply scrubbing all mode pages on driver
initialisation?
Reset it to a known state.
In this case, the driver
On Fri, Feb 04, 2011 at 02:36:04PM +0100, Manuel Bouyer wrote:
What then happens is very stupid. The driver calls
mpt_set_initial_config() in mpt.c which resets every 16 target device
pages to 0:
If we are not exposing these underlying target device pages as sd, then
you are right, we
On Fri, 4 Feb 2011, Thor Lancelot Simon wrote:
If the firmware vendor did *not* get it wrong, then there is a separate
page which holds these settings for the logical disk, and when we are
operating in RAID mode we need to use that one instead of ever accessing
the 16 pages for the physical
