From: Werner Almesberger <wa@almesberger.net>
To: bert hubert <ahu@ds9a.nl>, netdev@oss.sgi.com
Subject: Re: tc lockup on 2.4.19 up
Date: Mon, 8 Jul 2002 18:28:45 -0300 [thread overview]
Message-ID: <20020708182845.P1424@almesberger.net> (raw)
In-Reply-To: <20020708204858.GA16318@outpost.ds9a.nl>; from ahu@ds9a.nl on Mon, Jul 08, 2002 at 10:48:58PM +0200
bert hubert wrote:
> I think the rule gets matched circularly, but I'm unsure.
Indeed. Happens with tcsim too.
I need to think a bit about this one. As a work-around, you can use
tcc with -One, which generates a bunch of tests for equality instead
of the single negation.
Thanks,
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://icapeople.epfl.ch/almesber/_____________________________________/
prev parent reply other threads:[~2002-07-08 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 20:48 tc lockup on 2.4.19 up bert hubert
2002-07-08 21:28 ` Werner Almesberger [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=20020708182845.P1424@almesberger.net \
--to=wa@almesberger.net \
--cc=ahu@ds9a.nl \
--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).