All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Heinz <josef.k@mytomorrow.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb causes roaring penguin's pppoe daemon to terminate connection
Date: Sun, 10 Feb 2002 14:47:08 +0000	[thread overview]
Message-ID: <marc-lartc-101338666605777@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101328197705968@msgid-missing>

You wrote:

> And what one did you use for 2.4.16 ? 


There was a patch for 2.4.16 on http://luxik.cdi.cz/~devik/qos/htb/
It is no longer there but I can send you a diff against the
2.4.17 patch.

>>>you could try cbq instead. 
> 

 > ..

> :) I only need to determine whether the bug is related to
> change in htb, pppoe or kernel. If 2.4.16 worked then we need
> to minimize code size with the bug. 


OK, I'll make some tests.

> Try to use htb2_2.4.17.diff with 2.4.16 - it could say whether
> the bug is in htb (the diff should work with 2.4.16). 


Meanwhile I'm not so sure whether the problem is caused by htb.

I used the same htb script and made some tests using iperf.
I sent data over 4 parallel connections (2 tcp, 2 udp), so
that my upstream is full. This time pppoe did not die.

The times before when pppoe died there was always a h323
connection involved - at least I think so. So maybe the
problem is caused by the h323 patch I'm using.


>>Do think it would make sense to reduce the transmit queue on ppp0
>>from 200 to ... let's say 50 or 20?
> 
> probably not. The value is not used if you attached you own
> qdisc. It is only used as default size for default qdisc.


Ah, interesting. So my ifconfig $SOME_IF txqueuelen $SOME_QLEN

lines in the script can be thrown away.


Thank you for your tips. I'll analyze the situation in more detail
and report the results. I'm currently a bit short of time but
I should be able to find it out over the next few days.


Thomas

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

      parent reply	other threads:[~2002-02-10 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-09 19:07 [LARTC] htb causes roaring penguin's pppoe daemon to terminate connection Thomas Heinz
2002-02-09 21:05 ` [LARTC] htb causes roaring penguin's pppoe daemon to terminate Martin Devera
2002-02-09 22:24 ` [LARTC] htb causes roaring penguin's pppoe daemon to terminate connection Thomas Heinz
2002-02-09 22:41 ` [LARTC] htb causes roaring penguin's pppoe daemon to terminate Martin Devera
2002-02-10 14:47 ` Thomas Heinz [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-101338666605777@msgid-missing \
    --to=josef.k@mytomorrow.de \
    --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.