[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Resetting network device / skb leak

> 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

So you even do the final parts of state migration within the domain
that is migrating? That sounds hard to get right. :-)

 -- Keir

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
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.