From: Stefan Rompf <srompf@isg.de>
To: jamal <hadi@cyberus.ca>
Cc: davem@redhat.com, netdev@oss.sgi.com
Subject: Re: Patch resubmission: RFC2863 operstatus for 2.5.49
Date: Wed, 04 Dec 2002 00:04:09 +0100 [thread overview]
Message-ID: <3DED3869.5E47D7A2@isg.de> (raw)
In-Reply-To: Pine.GSO.4.30.0211290753590.3643-100000@shell.cyberus.ca
Hi Jamal,
> Just thought of something, it may be a little tricky but valuable and
> i am not quiet sure if it should part of your patch: We probably need to
> flush the qdiscs software queues; maybe even the DMA ring i.e simulate
> admin down followed by admin up.
dev_close() is doing quite a lot of stuff, so we should do nothing more
than flush the qdiscs when the link comes up. But is it really useful?
Normally, the queues are short anyway to keep latencies low, and fifty
additional packets don't hurt. I rather think about clearing neighbor
tables and the route cache whenever the operstatus goes down.
Anyway, implementation and usage of the notification should not mix up,
so it let it be a separate patch.
Stefan
next prev parent reply other threads:[~2002-12-03 23:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 9:22 Patch resubmission: RFC2863 operstatus for 2.5.49 Stefan Rompf
2002-11-26 10:15 ` David S. Miller
2002-11-26 15:36 ` Stefan Rompf
2002-12-03 22:22 ` Patch resubmission: RFC2863 operstatus for 2.5.50 Stefan Rompf
2002-12-04 0:52 ` Jeff Garzik
2002-12-04 9:44 ` Stefan Rompf
2002-12-04 18:15 ` Jeff Garzik
2002-12-04 13:11 ` jamal
2002-12-04 17:42 ` Jeff Garzik
2002-12-09 13:27 ` jamal
2002-12-09 23:10 ` Stefan Rompf
2002-12-10 3:55 ` Jeff Garzik
2002-12-12 13:21 ` jamal
2002-12-04 19:39 ` David S. Miller
2002-11-29 12:56 ` Patch resubmission: RFC2863 operstatus for 2.5.49 jamal
2002-12-03 23:04 ` Stefan Rompf [this message]
2002-12-04 13:06 ` jamal
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=3DED3869.5E47D7A2@isg.de \
--to=srompf@isg.de \
--cc=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.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).