[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: [dm-devel] Multipath and HSG80 phase 2
- From: "Duane Grigsby" <duane grigsby qlogic com>
- To: "device-mapper development" <dm-devel redhat com>, <christophe varoqui free fr>
- Cc:
- Subject: RE: [dm-devel] Multipath and HSG80 phase 2
- Date: Fri, 10 Dec 2004 10:33:05 -0800
yes, we plan on supporting this parameter as well.
-- duane
> -----Original Message-----
> From: dm-devel-bounces redhat com
> [mailto:dm-devel-bounces redhat com]On
> Behalf Of James Smart Emulex Com
> Sent: Friday, December 10, 2004 6:54 AM
> To: christophe varoqui free fr; dm-devel redhat com
> Cc: dm-devel redhat com
> Subject: RE: [dm-devel] Multipath and HSG80 phase 2
>
>
> > Indeed, the long delay is due to the tmo value ... leaving
> > the oops though :)
> > I'd like to set this param from the tools but don't want to
> > special-case every
> > other hardware.
> >
> > Do you plan on standardizing the parameter name ? Does Qlogic
> > provides a simalar
> > params through sysfs ?
>
> Well, as the fc transport patches (specifically for remote
> ports) complete, and the driver finally utilizes them without
> anything internal, you will have one fc transport parameter
> to tune - the dev_loss_tmo attribute on the
> fc_transport/<target> device. You would need to get the
> other FC drivers to start using these fc transport interfaces
> to make everything generic.
>
> -- james
>
> --
> dm-devel mailing list
> dm-devel redhat com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]