From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Wise Subject: Re: Problem with RDMA device removal architecture Date: Fri, 26 Mar 2010 11:53:41 -0500 Message-ID: <4BACE695.4010006@opengridcomputing.com> References: <4BACD985.1070906@opengridcomputing.com> <603F8A3875DCE940BA37B49D0A6EA0AE84CFD841@azsmsx501.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <603F8A3875DCE940BA37B49D0A6EA0AE84CFD841-uLM7Qlg6Mbekrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Tung, Chien Tin" Cc: Roland Dreier , linux-rdma , "Hefty, Sean" List-Id: linux-rdma@vger.kernel.org Tung, Chien Tin wrote: > [...] > > >> They also want >> to be able to "reset" a failed device (EEH events >> > > [...] > > >> 1) device A event happens causing the device to unregister itself with >> the RDMA core. This could be an EEH event requiring full device reset, >> or a OS hot-plug removal event. >> > > Just to nit-pick on terminology. When you say reset a device do you mean > adapter(or silicon) reset? In the case of multiport adapter, does that > mean all devices for that adapter will post RDMA_CM_EVENT_DEVICE_REMOVAL > event? > > I mean whatever you call a device and register it with the RDMA core via ib_register_device(). -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html