From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Gorm Hansen Subject: Re: Resetting network device / skb leak Date: Thu, 22 Apr 2004 12:23:30 +0200 Sender: xen-devel-admin@lists.sourceforge.net Message-ID: <1082629410.6924.6.camel@jacobg> References: Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Keir Fraser Cc: Xen list List-Id: xen-devel@lists.xenproject.org On Thu, 2004-04-22 at 08:19, Keir Fraser wrote: > The correct suspend behaviour is caused by executing dev->stop(). > > Why are you not able to run the existing ifdown/ifup code? It doesn't > execute notifier lists so shouldn't affect routing tables or anything > like that. Mainly because I need the interface to remain active across the point where I am checkpointing the system -- the interface is used in the migration which is still ongoing at that time (I firewall off unrelated connections to not mess things up externally). Basically I need to revive the (already open but not Xen-connected/initialised) interface when I wake up, which the previously quoted code does fine, but apparently this causes a leak of skbs. What I am looking for is a safe way of freeing or reusing the old ones before reinitialising the interface. Jacob ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click