From: Corey Hickey <bugfood-ml@fatooh.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 6/7] Make qdisc changeable.
Date: Tue, 31 Jul 2007 00:43:49 -0700 [thread overview]
Message-ID: <46AEE835.8060509@fatooh.org> (raw)
In-Reply-To: <46ADF18A.4060008@trash.net>
Patrick McHardy wrote:
> Corey Hickey wrote:
>> Re-implement sfq_change() and enable Qdisc_opts.change so "tc qdisc
>> change" will work.
>>
>> Signed-off-by: Corey Hickey <bugfood-ml@fatooh.org>
>> ---
>> net/sched/sch_sfq.c | 51 ++++++++++++++++++++++++++++++++++++++++++++++++++-
>> 1 files changed, 50 insertions(+), 1 deletions(-)
>>
>> diff --git a/net/sched/sch_sfq.c b/net/sched/sch_sfq.c
>> index e6a6a21..e042cd0 100644
>> --- a/net/sched/sch_sfq.c
>> +++ b/net/sched/sch_sfq.c
>> @@ -485,6 +485,55 @@ static int sfq_init(struct Qdisc *sch, struct rtattr *opt)
>> return 0;
>> }
>>
>> +static int sfq_change(struct Qdisc *sch, struct rtattr *opt)
>> +{
>> + struct sfq_sched_data *q = qdisc_priv(sch);
>> + struct sfq_sched_data tmp;
>> + struct sk_buff *skb;
>> + int err;
>> +
>> + /* set up tmp queue */
>> + memset(&tmp, 0, sizeof(struct sfq_sched_data));
>> + tmp.quantum = psched_mtu(sch->dev); /* default */
>
>
> If no value is given it should use the old value instead of
> reinitializing to the default.
>
>> + if ((err = sfq_q_init(&tmp, opt)))
>> + return err;
>
>
> This will also use defaults for all unspecified values. It would
> be more consistent with other qdiscs to only change those values
> that are actually specified, so something like "tc qdisc change ...
> perturb 10" will *only* change the perturbation parameter.
I somehow had it in my head that a qdisc change was supposed to work
that way. I'll change my patch.
> I'm not sure reusing the initialization function and copying the
> parameters is the best way to do this.
I'm not sure either, but I do like that it's conceptually simple and it
keeps the parameter handling in one place. I've thought and stared for a
while, and I don't see a better way, but that could of course be due to
my limited understanding and general newbiehood in that regard.
Thanks again for the review. I'll try to get a new batch of patches sent
off tomorrow.
-Corey
next prev parent reply other threads:[~2007-07-31 7:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 0:21 SFQ: backport some features from ESFQ (try 2) Corey Hickey
2007-07-30 0:21 ` [PATCH 1/7] Preparatory refactoring part 1 Corey Hickey
2007-07-30 13:51 ` Patrick McHardy
2007-07-31 1:26 ` Corey Hickey
2007-07-31 10:46 ` Patrick McHardy
2007-07-30 0:21 ` [PATCH 2/7] Preparatory refactoring part 2 Corey Hickey
2007-07-30 13:59 ` Patrick McHardy
2007-07-31 7:43 ` Corey Hickey
2007-07-30 0:21 ` [PATCH 3/7] Move two functions Corey Hickey
2007-07-30 0:21 ` [PATCH 4/7] Add "depth" Corey Hickey
2007-07-30 0:21 ` [PATCH 5/7] Add divisor Corey Hickey
2007-07-30 0:21 ` [PATCH 6/7] Make qdisc changeable Corey Hickey
2007-07-30 14:11 ` Patrick McHardy
2007-07-31 7:43 ` Corey Hickey [this message]
2007-08-06 2:47 ` Corey Hickey
2007-08-06 12:06 ` Patrick McHardy
2007-07-30 0:21 ` [PATCH 7/7] Remove comments about hardcoded values Corey Hickey
2007-07-30 0:21 ` [PATCH] [iproute2] SFQ: Support changing depth and divisor Corey Hickey
-- strict thread matches above, loose matches on Subject: below --
2007-07-29 7:08 [PATCH 0/7] SFQ: backport some features from ESFQ Corey Hickey
2007-07-29 7:08 ` [PATCH 1/7] Preparatory refactoring part 1 Corey Hickey
2007-07-29 7:08 ` [PATCH 2/7] Preparatory refactoring part 2 Corey Hickey
2007-07-29 7:08 ` [PATCH 3/7] Move two functions Corey Hickey
2007-07-29 7:08 ` [PATCH 4/7] Add "depth" Corey Hickey
2007-07-29 7:08 ` [PATCH 5/7] Add divisor Corey Hickey
2007-07-29 7:08 ` [PATCH 6/7] Make qdisc changeable Corey Hickey
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=46AEE835.8060509@fatooh.org \
--to=bugfood-ml@fatooh.org \
--cc=kaber@trash.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).