Date: Fri, 01 Oct 2010 00:00:36 +0300 From: Alexander Motin <mav@FreeBSD.org> To: Andriy Gapon <avg@icyb.net.ua> Cc: FreeBSD-Current <freebsd-current@FreeBSD.org> Subject: Re: letting glabel recognise a media change Message-ID: <4CA4FA74.8000708@FreeBSD.org> In-Reply-To: <4CA4F6FF.5070402@icyb.net.ua> References: <4CA3BD7C.9080306@feral.com> <mailpost.1285845776.1043534.73790.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw> <4CA4CCE3.9060408@FreeBSD.org> <4CA4F6FF.5070402@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Andriy Gapon wrote: > on 30/09/2010 20:46 Alexander Motin said the following: >> Andriy Gapon wrote: >>> on 30/09/2010 01:28 Matthew Jacob said the following: >>>> If something like that was in place, I assure you that things would start to use >>>> it very quickly. >>> I am not sure about this. >>> Because, e.g. I don't see an easy way to know that media is changed in scsi_cd >>> driver. That is, without polling. I don't consider polling to be an easy way for >>> a number of reasons. >> SATA specification defines concept of Asynchronous Notification. It is >> already used by port multipliers to report about PHY events. It is also >> supposed to be used by CD drives to report media change. I haven't seen >> such devices yet, but hope they may appear sometimes. > > Would this require some reverse-path from SIM driver to peripheral driver to > deliver a notification? Do we have one? Yes we do. SATA PMP driver (it looks like usual peripheral driver from this point) already receives and handles AC_SCSI_AEN messages sent to it via xpt_async() mechanism. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CA4FA74.8000708>