netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: safari-kernel@safari.iki.fi
Cc: Linux Networking Mailing List <netdev@vger.kernel.org>
Subject: Re: updated tcatm patches for kernel/iproute 2.6.22
Date: Thu, 19 Jul 2007 15:22:09 +0200	[thread overview]
Message-ID: <469F6581.3020400@trash.net> (raw)
In-Reply-To: <20070719113559.4y2z4bj4vwtglupw@m.safari.iki.fi>

Sami Farin wrote:
> On Thu, Jul 19, 2007 at 00:58:44 +0200, Patrick McHardy wrote:
>   
>> Let me repeat again before we get in an endless discussion
>> again - I will NACK these patches until we have a solution
>> that works for all qdiscs.
>>     
>
> I googled for
> "Accurate packet scheduling for ATM" mchardy
> and found some threads from 2006.
>   
> http://www.mail-archive.com/netdev@vger.kernel.org/msg15706.html
> http://www.mail-archive.com/netdev@vger.kernel.org/msg21395.html
>
> So, Patrick:

Please keep me as receipient or CC when talking to me.

> 1) what is this "solution"?  do you have code?
>    or a brief explanation...

Simply calculcate the length including additional encapsulation
overhead at runtime. This allows all qdiscs to use the wire-length
in their calculations.

> 2) are you still working on this? is somebody else?
>   

Not to my knowledge.

> 3) do you have patches for iproute/kernel 2.6.22?

No.

> 4) if you have some patches, but they are not yet
>    complete, what else needs to be done?
>   

Not sure, its been a while since I posted some example patches.
Its not much work, probably quicker to start over.


      reply	other threads:[~2007-07-19 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 21:06 updated tcatm patches for kernel/iproute 2.6.22 Sami Farin
2007-07-18 22:39 ` Stephen Hemminger
2007-07-18 22:58 ` Patrick McHardy
2007-07-19 11:35   ` Sami Farin
2007-07-19 13:22     ` Patrick McHardy [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=469F6581.3020400@trash.net \
    --to=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=safari-kernel@safari.iki.fi \
    /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).