[Openib-windows] RE: [patch] cl_signal_osd.h

[Eitan Zahavi]

Hi 

Clarification: The ^C was introduced long ago (~2years) into the code in
order to avoid resource loss that happened in IBAL. Later it proved itself
useful when the Gen1 was introduced. Today, I am not aware of any issue with
resources leaks etc. So practically one could stop catching ^C and probably
everything will work right in the OpenIB access layer. 

Sorry about my improper misleading previous mail.

Eitan


 -----Original Message-----
From: 	Sean Hefty [mailto:sean.hefty at intel.com] 
Sent:	Wednesday, July 13, 2005 7:39 PM
To:	'Eitan Zahavi'; 'Fab Tillier'; Yossi Leybovich
Cc:	Aviram Gutman; openib-windows at openib.org; Windows Group
Subject:	RE: [Openib-windows] RE: [patch] cl_signal_osd.h

Thanks for the useful note. 
We currently catch ^C for OpenSM and OSMV to cleanup resources that would be
lost or create kernel oops. I guess that in Windows environment this is not
a
must.


If you need to catch ctrl-C to prevent a kernel oops, then something is
wrong
with the implementation.  I would think the same thing about cleanup.

- Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20050714/6d387171/attachment.html>