From: Catalin BOIE <catab@deuroconsult.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb_change sfq_change
Date: Thu, 16 May 2002 10:52:58 +0000 [thread overview]
Message-ID: <marc-lartc-102154647309061@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102092163411520@msgid-missing>
On Wed, 15 May 2002, Martin Devera wrote:
> Date: Wed, 15 May 2002 15:11:09 +0200 (CEST)
> From: Martin Devera <devik@cdi.cz>
> To: Catalin BOIE <catab@deuroconsult.ro>
> Cc: lartc@mailman.ds9a.nl
> Subject: Re: [LARTC] htb_change sfq_change
>
> > > :) You can drop & recreate it safely. User will
> > > not see it. The change function for SFQ will be
> > > probably considered "redundant" by other kernel
> > > developers because of it.
> >
> > But you loose counters! This is bad IMHO.
>
> That's good point ! So that go ahead and implement it for
> SFQ :)
But it is already!
But in sch_sfq.c at the end (in jump table) is "NULL /* sfq_change */"!
There are race problems in sfq_change?
I found a patch on the net that puted NULL instead sfq_change...
Thanks!
---
Catalin(ux) BOIE
catab@deuroconsult.ro
openh323://dino.rdsbv.ro
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-05-16 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 5:19 [LARTC] htb_change sfq_change Catalin BOIE
2002-05-09 10:29 ` Martin Devera
2002-05-10 6:41 ` Catalin BOIE
2002-05-10 9:58 ` Catalin BOIE
2002-05-10 10:45 ` Martin Devera
2002-05-10 12:49 ` Martin Devera
2002-05-14 9:02 ` Catalin BOIE
2002-05-14 9:05 ` Catalin BOIE
2002-05-14 12:13 ` Martin Devera
2002-05-14 12:15 ` Martin Devera
2002-05-15 11:24 ` Catalin BOIE
2002-05-15 13:04 ` Michael T. Babcock
2002-05-15 13:11 ` Martin Devera
2002-05-16 10:52 ` Catalin BOIE [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=marc-lartc-102154647309061@msgid-missing \
--to=catab@deuroconsult.ro \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.