From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jesper Dangaard Brouer <hawk@comx.dk>
Cc: Stephen Hemminger <shemminger@osdl.org>,
Jamal Hadi Salim <hadi@cyberus.ca>,
netdev@vger.kernel.org, lartc@mailman.ds9a.nl,
russell-tcatm@stuart.id.au, hawk@diku.dk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] NET: Accurate packet scheduling for ATM/ADSL (userspace)
Date: Wed, 14 Jun 2006 11:57:05 +0100 [thread overview]
Message-ID: <1150282625.3490.23.camel@localhost.localdomain> (raw)
In-Reply-To: <1150278040.26181.37.camel@localhost.localdomain>
Ar Mer, 2006-06-14 am 11:40 +0200, ysgrifennodd Jesper Dangaard Brouer:
> option to calculate traffic transmission times (rate table)
> over all ATM links, including ADSL, with perfect accuracy.
<Pedant>
Only if the lowest level is encoded in a time linear manner. If you are
using NRZ, NRZI etc at the bottom level then you may still be out...
</Pedant>
The other problem I see with this code is it is very tightly tied to ATM
cell sizes, not to solving the generic question of packetisation. I'm
not sure if that matters but for modern processors I'm also sceptical
that the clever computation is actually any faster than just doing the
maths, especially if something cache intensive is also running.
Alan
next prev parent reply other threads:[~2006-06-14 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 9:40 [PATCH 2/2] NET: Accurate packet scheduling for ATM/ADSL (userspace) Jesper Dangaard Brouer
2006-06-14 10:57 ` Alan Cox [this message]
2006-06-14 13:18 ` Jesper Dangaard Brouer
2006-06-15 0:47 ` Russell Stuart
2006-06-15 13:03 ` jamal
2006-06-19 19:31 ` Jesper Dangaard Brouer
2006-06-20 14:06 ` jamal
2006-06-20 14:45 ` Patrick McHardy
2006-06-20 15:38 ` jamal
2006-06-20 16:51 ` Patrick McHardy
2006-06-22 19:02 ` jamal
2006-06-23 15:05 ` Patrick McHardy
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=1150282625.3490.23.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hadi@cyberus.ca \
--cc=hawk@comx.dk \
--cc=hawk@diku.dk \
--cc=lartc@mailman.ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=russell-tcatm@stuart.id.au \
--cc=shemminger@osdl.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).