RE: kdump detection in SCSI drivers
How do we know when little memory is available? Other suggestion which came about was to parse the kernel command line and look for elfcorehdr=. Is this ok? Is kernel command line visible to the SCSI drivers? Thanks -Atul -Original Message- From: Pavel Machek [mailto:[EMAIL PROTECTED] Sent: Thursday, September 20, 2007 6:43 AM To: Mukker, Atul Cc: Linux-scsi@vger.kernel.org; [EMAIL PROTECTED] Subject: Re: kdump detection in SCSI drivers Hi, Is there a standard way for drivers (RAID) to detect if the current kernel is running in kdump mode? We would like to adjust driver behavior dynamically when kdump is active by scaling down resources. Perhaps you should be automatically using little resources when little memory is available, or something? With upcomping kjump patches, it is more interesting than kdump vs. no kdump. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
kdump detection in SCSI drivers
Hi, Is there a standard way for drivers (RAID) to detect if the current kernel is running in kdump mode? We would like to adjust driver behavior dynamically when kdump is active by scaling down resources. Thanks -Atul Mukker LSI Corp. - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: How to add/drop SCSI drives from within the driver?
And what do you mean different implementations for /sbin/hotplug? What distros do not use the standard linux-hotplug type scripts, or if not the scripts, the same functionality? You are right, even though distributions (I checked Red Hat and SuSE) have different /sbin/hotplug scripts (e.g., SuSE 9.2 will not execute files from /etc/hotplug.d whereas Red Hat does) udev will be invoked in all cases, which will take care of creating device nodes. But our concern is that how would the applications get the cue that udev has actually created the nodes for the new devices? Make sure an agent is called after the, e.g., scsi agents are executed from /etc/hotplug directory (which happen to be scsi.agent, scsi_device.agent, scsi_host.agent in one and only scsi.agent in other distribution), by writing an rc like script? Or more likely, by placing our agent in /etc/dev.d directory. Unfortunately, there seems be not a consensus here as well. On system has default and net directories and other has block, input, net, tty? Thanks Atul Mukker Architect, RAID Drivers and BIOS LSI Logic Corporation - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: How to add/drop SCSI drives from within the driver?
Thanks for the suggestion. After more exploration, looks like different distribution have different implementations for /sbin/hotplug. This may aggravate the issue for applications. For now, we will stick with a wait and watch after bus scan :-( Will probe the [EMAIL PROTECTED] list for more pointers Thanks === Atul Mukker Architect, Drivers and BIOS LSI Logic Corporation -Original Message- From: Patrick Mansfield [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 25, 2005 11:52 AM To: Mukker, Atul Cc: 'James Bottomley'; Linux Kernel; SCSI Mailing List Subject: Re: How to add/drop SCSI drives from within the driver? Atul - On Tue, Jan 25, 2005 at 11:27:36AM -0500, Mukker, Atul wrote: After writing the - - - to the scan attribute, the management applications assume the udev has created the relevant entries in the /dev directly and try to use the devices _immediately_ and fail to see the devices Is there a hotplug event which would tell the management applications that the device nodes have actually been created now and ready to be used? Read the udev man page section, the part right before FILES. Try putting a script under /etc/dev.d/default/*.dev. Then you can get more specific with an /etc/dev.d/scsi/*.dev script or something else. I just tried something simple but did not get it working. Try [EMAIL PROTECTED] list for help. -- Patrick Mansfield - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
