From: Andi Kleen <ak@suse.de>
To: Christopher Friesen <cfriesen@nortelnetworks.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: RFC: ethernet links should remember routes the same as addresses
Date: Thu, 29 Nov 2001 22:18:41 +0100 [thread overview]
Message-ID: <20011129221841.A14979@wotan.suse.de> (raw)
In-Reply-To: <3C068ED1.D5E2F536@nortelnetworks.com.suse.lists.linux.kernel> <p73r8qhqrmi.fsf@amdsim2.suse.de> <3C06A1C8.C133F725@nortelnetworks.com>
In-Reply-To: <3C06A1C8.C133F725@nortelnetworks.com>; from cfriesen@nortelnetworks.com on Thu, Nov 29, 2001 at 03:59:52PM -0500
On Thu, Nov 29, 2001 at 03:59:52PM -0500, Christopher Friesen wrote:
> Unfortunately, this seems to only list the routes in the main routing table, and
> these routes are recreated automatically when I bring the link back up.
Well, it is not that hard to extend it.
Just iterate over ip rule ls output too.
(left as an exercise for the reader)
> If the driver re-init is totally separate from the routing code, is there any
> real reason why shutting down the driver *should* remove all routes to that
> device? Maybe the simplest solution would be a new ioctl that would be a link
> *reset*...just down/up the link without affecting anything else....
If you just want to do a link reset you can use ethertool today with most
drivers. What is different is a full driver reset to work around software/
hardware bugs. That would need to be a new ioctl.
-Andi
next prev parent reply other threads:[~2001-11-29 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C068ED1.D5E2F536@nortelnetworks.com.suse.lists.linux.kernel>
2001-11-29 19:55 ` Andi Kleen
2001-11-29 20:59 ` Christopher Friesen
2001-11-29 21:03 ` Ben Greear
2001-11-29 21:18 ` Christopher Friesen
2001-11-29 21:18 ` Andi Kleen [this message]
2001-11-29 23:04 Julian Anastasov
[not found] <9u64q7$46m$1@phoenix.clouddancer.com>
2001-11-29 19:38 ` Christopher Friesen
2001-11-29 20:58 ` Colonel
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=20011129221841.A14979@wotan.suse.de \
--to=ak@suse.de \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®