public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Dake <sdake@mvista.com>
To: Michael Clark <michael@metaparadigm.com>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] [PATCHES] Advanced TCA Hotswap Support in Linux Kernel
Date: Tue, 15 Oct 2002 12:28:59 -0700	[thread overview]
Message-ID: <3DAC6C7B.1080205@mvista.com> (raw)
In-Reply-To: 3DAC685B.9070102@metaparadigm.com


Michael Clark wrote:

> On 10/16/02 01:38, Steven Dake wrote:
>
>> At this point, there isn't anything using them.  I am working on a 
>> hotswap manager, that may be in kernel space (for performance 
>> reasons) that may use these interfaces.  I'm also working on a SAFTE 
>> Hotswap processor module (ie; drivers/scsi/sp.c) for the SCSI 
>> subsystem that uses these interfaces.  (Safte is a hotswap standard 
>> for SCSI chassis).
>
>
> Do you really want to have SAF-TE polling in the kernel?

Good code thanks for the pointer.

When I searched months ago, there wasn't anything out there.

Safte polling in the kernel isn't inherently bad and could be tied into 
the hotplug mechanism.

Making SAFTE hotswap available via SG would also work but system 
performance would be bad at small poll intervals (like 100 msec).

Thanks
-steve

>
> This can easily be accomplished in userspace using sg.
>
> safte-monitor <http://gort.metaparadigm.com/safte-monitor/> can already
> provde disk insertion, removal notifications in userspace and already
> supports calling out to a script with the physical slot location 
> information
> (and with tweaks to the code, scsi device of the disk inserted)
>
> There is even code in safte-monitor to identify the wwn of the devices
> in each slot, although it needs updating to the latest qlogic ioctl
> interface (or hbaapi).
>
> ~mc
>
>
>


  reply	other threads:[~2002-10-15 19:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-14 18:42 [ANNOUNCE] [PATCHES] Advanced TCA Hotswap Support in Linux Kernel Steven Dake
2002-10-15  0:59 ` Greg KH
2002-10-15 18:39   ` Steven Dake
2002-10-15 20:42     ` Greg KH
2002-10-15  5:29 ` Greg KH
2002-10-15 17:38   ` Steven Dake
2002-10-15 19:11     ` Michael Clark
2002-10-15 19:28       ` Steven Dake [this message]
2002-10-15 20:34         ` Greg KH
2002-10-15 20:46           ` Steven Dake
2002-10-15 20:54             ` Greg KH
2002-10-15 21:07               ` Steven Dake
2002-10-15 21:16                 ` Greg KH
2002-10-15 21:48                   ` Steven Dake
2002-10-16  1:05             ` Michael Clark
2002-10-15 20:52     ` Greg KH
     [not found]       ` <3DAC89FA.9000505@mvista.com>
2002-10-15 22:04         ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DAC6C7B.1080205@mvista.com \
    --to=sdake@mvista.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@metaparadigm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox