From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Khapyorsky Subject: Re: [PATCH] opensm/mcast_tbl: set max_mlid_ho as actually configured mlid Date: Mon, 2 Nov 2009 18:43:43 +0200 Message-ID: <20091102164343.GJ21323@me> References: <4AEAEA86.8080309@systemfabricworks.com> <20091030200620.GB5829@me> <20091030213125.GE5829@me> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Hal Rosenstock Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-rdma@vger.kernel.org On 12:18 Mon 02 Nov , Hal Rosenstock wrote: > > > > Yet another (likely even more efficient) approach would be memset()ing > > MFTs in realloc function above requested mlid_offset, then we will be > > able to remove osm_mcast_tbl_clear_mlid() completely. > > Isn't mlid clearing done on a per mlid basis rather than based on > above some mlid (offset) ? Also and perhaps more significantly, an > mlid can be removed in the middle of a range of mlids. So I don't see > how clear_mlid can be removed. Yes, correct, we cannot remove clear_mlid completely. Sasha -- 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