Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 03 Mar 2003 13:49:49 -0700
From:      "Justin T. Gibbs" <gibbs@scsiguy.com>
To:        Nate Lawson <nate@root.org>, Hidetoshi Shimokawa <simokawa@sat.t.u-tokyo.ac.jp>
Cc:        non@ever.sanda.gr.jp, freebsd-scsi@freebsd.org
Subject:   Re: call scan_bus in interrupt context.
Message-ID:  <1600480000.1046724589@aslan.btc.adaptec.com>
In-Reply-To: <Pine.BSF.4.21.0303031234370.78538-100000@root.org>
References:   <Pine.BSF.4.21.0303031234370.78538-100000@root.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> I waited for someone else to ask this question but no one did so I will:  
> "Why do you have to do this?"  Couldn't you use a condition variable to
> signal a kthread telling it "rescan needed"?  Could you set a flag that
> rescan is needed and check it in the open() call and perform a rescan
> there if necessary?  I see a lot of ways to avoid rescanning in an
> interrupt context.

Sure, but the main point is that CAM should have facilities to do this
for you so that each driver doesn't have to re-invent the wheel.

--
Justin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1600480000.1046724589>