linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Question on routing hotplug events to open-ipmi interface
@ 2006-08-18  6:07 Krishna Pidamale
  2006-08-18 11:28 ` Kay Sievers
  2006-08-19  1:02 ` Krishna Pidamale
  0 siblings, 2 replies; 3+ messages in thread
From: Krishna Pidamale @ 2006-08-18  6:07 UTC (permalink / raw)
  To: linux-hotplug

My system has plenty of hotpluggable SATA drives, and system runs either SLES or RHEL (older and newer distributions). Through /etc/hotplug/scsi.agent I could verify all hotplug add and remove events with DEVPATH. I would like to pass these event info to OPEN-IPMI interface, which means I will write a small C 
program to do this. Can I execute this program from scsi.agent? I am concerned about performance hit due to "n" instances of this executable. Since drives can be added/removed several times, it could add up many events. 

Is this /sbin/hotplug utility meant for such operation? Any suggestions to avoid performance degradation? How can udev help here? Where can I find additional information? 

-Krishna









-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Question on routing hotplug events to open-ipmi interface
  2006-08-18  6:07 Question on routing hotplug events to open-ipmi interface Krishna Pidamale
@ 2006-08-18 11:28 ` Kay Sievers
  2006-08-19  1:02 ` Krishna Pidamale
  1 sibling, 0 replies; 3+ messages in thread
From: Kay Sievers @ 2006-08-18 11:28 UTC (permalink / raw)
  To: linux-hotplug

On Thu, 2006-08-17 at 23:07 -0700, Krishna Pidamale wrote:
> My system has plenty of hotpluggable SATA drives, and system runs either SLES or RHEL (older and newer distributions). Through /etc/hotplug/scsi.agent I could verify all hotplug add and remove events with DEVPATH. I would like to pass these event info to OPEN-IPMI interface, which means I will write a small C 
> program to do this. Can I execute this program from scsi.agent? I am concerned about performance hit due to "n" instances of this executable. Since drives can be added/removed several times, it could add up many events. 
> 
> Is this /sbin/hotplug utility meant for such operation? Any suggestions to avoid performance degradation? How can udev help here? Where can I find additional information? 

Depends on the size of you box. The only sane thing you can do
with /sbin/hotplug is to disable it. :) It's simply a fork-bomb that
kills your box when you generate a lot of events.

Old SLES kernels have kernel code, to limit the number of parallel
running /sbin/hotplug processes, standard kernels may create
out-of-memory situations on big boxes.

Newer udev versions connect with the udevd daemon to the kernel over a
netlink socket and don't exec() a binary for every event. Also the
created system load created by event handlers is limited by udevd.

There is no way to work with /sbin/hotplug in a performance critical
setup or on big boxes. Use a newer distro release with a recent kernel
+udev, if you expect a lot of events. Everything else may work, but if
your setup creates more than the usual number of events you may not even
be able to bootup with /sbin/hotplug in use.

Thanks,
Kay


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Question on routing hotplug events to open-ipmi interface
  2006-08-18  6:07 Question on routing hotplug events to open-ipmi interface Krishna Pidamale
  2006-08-18 11:28 ` Kay Sievers
@ 2006-08-19  1:02 ` Krishna Pidamale
  1 sibling, 0 replies; 3+ messages in thread
From: Krishna Pidamale @ 2006-08-19  1:02 UTC (permalink / raw)
  To: linux-hotplug

THANK YOU  Kay  for your input,  let me dig udevd and more.

-Krishna


Sievers wrote:

>On Thu, 2006-08-17 at 23:07 -0700, Krishna Pidamale wrote:
>  
>
>>My system has plenty of hotpluggable SATA drives, and system runs either SLES or RHEL (older and newer distributions). Through /etc/hotplug/scsi.agent I could verify all hotplug add and remove events with DEVPATH. I would like to pass these event info to OPEN-IPMI interface, which means I will write a small C 
>>program to do this. Can I execute this program from scsi.agent? I am concerned about performance hit due to "n" instances of this executable. Since drives can be added/removed several times, it could add up many events. 
>>
>>Is this /sbin/hotplug utility meant for such operation? Any suggestions to avoid performance degradation? How can udev help here? Where can I find additional information? 
>>    
>>
>
>Depends on the size of you box. The only sane thing you can do
>with /sbin/hotplug is to disable it. :) It's simply a fork-bomb that
>kills your box when you generate a lot of events.
>
>Old SLES kernels have kernel code, to limit the number of parallel
>running /sbin/hotplug processes, standard kernels may create
>out-of-memory situations on big boxes.
>
>Newer udev versions connect with the udevd daemon to the kernel over a
>netlink socket and don't exec() a binary for every event. Also the
>created system load created by event handlers is limited by udevd.
>
>There is no way to work with /sbin/hotplug in a performance critical
>setup or on big boxes. Use a newer distro release with a recent kernel
>+udev, if you expect a lot of events. Everything else may work, but if
>your setup creates more than the usual number of events you may not even
>be able to bootup with /sbin/hotplug in use.
>
>Thanks,
>Kay
>
>  
>



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-08-19  1:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-18  6:07 Question on routing hotplug events to open-ipmi interface Krishna Pidamale
2006-08-18 11:28 ` Kay Sievers
2006-08-19  1:02 ` Krishna Pidamale

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).