netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Pokrywka <wolfmoon@o2.pl>
To: eric.dumazet@gmail.com
Cc: kaber@trash.net, soltys@ziu.info, akpm@linux-foundation.org,
	netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
	hadi@cyberus.ca, lucas.bocchi@gmail.com, 631945@bugs.debian.org,
	00bormoj@gmail.com, fdelawarde@wirelessmundi.com
Subject: Bug#631945: [Bugme-new] [Bug 39372] New: Problems with HFSC Scheduler
Date: Thu, 04 Aug 2011 15:55:15 +0200	[thread overview]
Message-ID: <344feff5.16ac6e1d.4e3aa4c3.49362@o2.pl> (raw)

From: Michal Soltys <soltys@ziu.info>
Date: Fri, 29 Jul 2011 14:29:10 +0200

>> On 11-07-22 11:58, Michal Pokrywka wrote:
>> 
>> commit b262a5da755cc6ed0cb4fba230cd9bf4037e1096 sch_sfq: fix peek()
>> implementation
>> 
>> and
>> 
>> commit 9df49f2bfe862573911a080c75a6d81113c5c81d sch_sfq: avoid giving
>> spurious NET_XMIT_CN signals
>> 
>> Reverting these patches makes HFSC work again.
>> 
>
> This one (upstream 8efa885406359af300d46910642b50ca82c0fe47) seems to be
> the culprit (does reverting only that one cures the problem ?)

Yes, indeed. Commit b262a5da755cc6ed0cb4fba230cd9bf4037e1096 is irrelevant.

Patch "sch_sfq: fix sfq_enqueue()" (provided by Eric Dumazet) applied to 2.6.39.1 fixes the problem, and hfsc+sfq works as expected.

             reply	other threads:[~2011-08-04 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 13:55 Michal Pokrywka [this message]
     [not found] <bug-39372-10286@https.bugzilla.kernel.org/>
2011-07-14 22:14 ` [Bugme-new] [Bug 39372] New: Problems with HFSC Scheduler Andrew Morton
2011-07-29 12:29   ` Bug#631945: " Michal Soltys

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=344feff5.16ac6e1d.4e3aa4c3.49362@o2.pl \
    --to=wolfmoon@o2.pl \
    --cc=00bormoj@gmail.com \
    --cc=631945@bugs.debian.org \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=eric.dumazet@gmail.com \
    --cc=fdelawarde@wirelessmundi.com \
    --cc=hadi@cyberus.ca \
    --cc=kaber@trash.net \
    --cc=lucas.bocchi@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=soltys@ziu.info \
    /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).