Date: Fri, 18 Nov 2005 08:10:29 -0700 From: Scott Long <scottl@samsco.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: John Polstra <jdp@FreeBSD.org>, cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, Lukas Ertl <le@FreeBSD.org> Subject: Re: cvs commit: src/sys/cam/scsi scsi_cd.c scsi_da.c src/sys/geom geom_disk.c geom_disk.h geom_subr.c Message-ID: <437DEEE5.9040201@samsco.org> In-Reply-To: <7052.1132309178@critter.freebsd.dk> References: <7052.1132309178@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp wrote: > In message <437D94EA.90909@samsco.org>, Scott Long writes: > >>Lukas Ertl wrote: > > >>What does this mean for other drivers? RAID arrays can come and go >>at runtime, either due to drive failure or due to actions by the user >>via a management app. I don't recall ever seeing a problem like this >>with the aac driver and creating/destroying arrays in a loop at runtime. > > > Most drivers seem to detach their internal state from the struct > disk, and therefore they don't need this. > So what makes CAM special in this regard? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?437DEEE5.9040201>