From: Badalian Vyacheslav <slavon@bigtelecom•ru>
To: Jesper Dangaard Brouer <hawk@diku•dk>
Cc: "Duyck, Alexander H" <alexander.h.duyck@intel•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"shemminger@vyatta•com" <shemminger@vyatta•com>
Subject: Re: can't apply sch_multiq
Date: Sun, 11 Jan 2009 09:06:20 +0300 [thread overview]
Message-ID: <49698C5C.6040609@bigtelecom.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0901071304130.11851@ask.diku.dk>
Thanks all!
I hope iproute2 build release for new features what added at 2.6.28 =)
Best regals, Badalian Vyacheslav
>
> On Tue, 6 Jan 2009, Duyck, Alexander H wrote:
>
>> Badalian Vyacheslav wrote:
>>> Hello all.
>>> kernel 2.6.28, iproute2 - 2.6.26 (last release)
>>>
>> The only part that is probably missing is that I don't believe the
>> sch_multiq patch been accepted into the iproute2. Once that is in
>> then tc should work with the multiq qdisc without any issues.
>
> You can use the lastest iproute2 git tree at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git
>
> I just checked that the sch_multiq changes have been added to this
> tree (although it looks like Stephen just added that patch yesterday ;-))
>
> Cheers,
> Jesper Brouer
>
> --
> -------------------------------------------------------------------
> MSc. Master of Computer Science
> Dept. of Computer Science, University of Copenhagen
> Author of http://www.adsl-optimizer.dk
> -------------------------------------------------------------------
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger•kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2009-01-11 6:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 10:57 can't apply sch_multiq Badalian Vyacheslav
2009-01-06 16:50 ` Duyck, Alexander H
2009-01-07 12:10 ` Jesper Dangaard Brouer
2009-01-11 6:06 ` Badalian Vyacheslav [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=49698C5C.6040609@bigtelecom.ru \
--to=slavon@bigtelecom$(echo .)ru \
--cc=alexander.h.duyck@intel$(echo .)com \
--cc=hawk@diku$(echo .)dk \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@vyatta$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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