From: Stefan Rompf <srompf@isg.de>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: netdev@oss.sgi.com, "Cramer, Jeb J" <jeb.j.cramer@intel.com>
Subject: Re: Flush Tx skbs after link down
Date: Wed, 15 Jan 2003 10:50:33 +0100 [thread overview]
Message-ID: <3E252EE9.D8CA8EDC@isg.de> (raw)
In-Reply-To: C6F5CF431189FA4CBAEC9E7DD5441E01087ADF@orsmsx402.jf.intel.com
Hi,
> Someone most know the answer to this: What's the proper way to dispose
> of Tx skbs that are owned by the h/w ("in-flight") when link was lost?
I think this can't be achieved without driver support, simply because
pending DMA transfers must be removed before freeing the skbs, and this
is specific. So the driver model needs to be extended to have a reset
method similiar to the qdiscs. If available, this method is called on
link down event by the linkwatch stuff included in recent 2.5 kernels.
Stefan
next prev parent reply other threads:[~2003-01-15 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 8:31 Flush Tx skbs after link down Feldman, Scott
2003-01-15 9:50 ` Stefan Rompf [this message]
2003-01-15 9:57 ` Stefan Rompf
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=3E252EE9.D8CA8EDC@isg.de \
--to=srompf@isg.de \
--cc=jeb.j.cramer@intel.com \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).