From: Jacob Gorm Hansen <jacob@melon.dk>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen list <xen-devel@lists.sourceforge.net>
Subject: Re: Resetting network device / skb leak
Date: Thu, 22 Apr 2004 12:23:30 +0200 [thread overview]
Message-ID: <1082629410.6924.6.camel@jacobg> (raw)
In-Reply-To: <E1BGXYI-0001oh-00@mta1.cl.cam.ac.uk>
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
next prev parent reply other threads:[~2004-04-22 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 17:38 Resetting network device / skb leak Jacob Gorm Hansen
2004-04-22 6:19 ` Keir Fraser
2004-04-22 10:23 ` Jacob Gorm Hansen [this message]
2004-04-22 10:28 ` Keir Fraser
2004-04-22 10:46 ` Jacob Gorm Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1082629410.6924.6.camel@jacobg \
--to=jacob@melon.dk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.