netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Rompf <srompf@isg.de>
To: "Feldman, Scott" <scott.feldman@intel.com>,
	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:57:42 +0100	[thread overview]
Message-ID: <3E253096.9F9DB6FE@isg.de> (raw)
In-Reply-To: 3E252EE9.D8CA8EDC@isg.de


> 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

PS: We also need to avoid that new skbs are enqueued while the link is
down without making the critical code path in dev_queue_xmit() much
longer. Right now, I don't have any ideas beyond a proof of concept for
this part.

Stefan

      reply	other threads:[~2003-01-15  9:57 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
2003-01-15  9:57   ` Stefan Rompf [this message]

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=3E253096.9F9DB6FE@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).