Date: Thu, 15 Feb 2007 21:41:08 -0700 From: Scott Long <scottl@samsco.org> To: mjacob@freebsd.org Cc: freebsd-scsi@freebsd.org Subject: Re: CAM rescanner thread? Message-ID: <45D535E4.60609@samsco.org> In-Reply-To: <20070215175554.X56445@ns1.feral.com> References: <20070104225519.Q92958@ns1.feral.com> <459E8AE7.90104@samsco.org> <20070105093930.Y34456@ns1.feral.com> <459E97E6.4000603@samsco.org> <459E989C.2020602@samsco.org> <20070105103431.A34456@ns1.feral.com> <20070105104021.D34456@ns1.feral.com> <45A9225D.4080907@scsiguy.com> <20070215145657.N45611@ns1.feral.com> <45D4F7C8.7050903@samsco.org> <20070215175554.X56445@ns1.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The goal was to create sys/cam/scsi/scsi_probe.c and start divorcing the SCSI knowledge from the XPT. Having it be a thread was just a side effect. Unfortunately, I haven't been able to finish that work yet. It's getting closer, though. But seriously, I saw little specific benefit to it being a separate thread rather than part of the camisr. Scanning/probing doesn't block, so it's not like it's blocking the camisr from processing other I/O. It's just nice from a modularity standpoint. Scott mjacob@freebsd.org wrote: > > And you didn't check it in because....? > > > On Thu, 15 Feb 2007, Scott Long wrote: > >> Matthew Jacob wrote: >>> >>> Following up from this, belatedly, I see lots of good stuff, and: >>> >>> >>>> With the discovery process moved to a >>>> thread and some augmentation to XPT_SCAN_*, we should be good enough >>>> for now. >>> >>> So, in principle a thread for rescanning seems appropriate to you? >>> >>> -matt >>> >> >> I've had various prototypes of this in the past. >> >> Scott >> >>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45D535E4.60609>