From: Russell Stuart <russell@stuart.id.au>
To: Patrick McHardy <kaber@trash.net>
Cc: Russell Stuart <russell-tcatm@stuart.id.au>,
hadi@cyberus.ca, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Stephen Hemminger <shemminger@osdl.org>,
netdev@vger.kernel.org, Jesper Dangaard Brouer <hawk@diku.dk>
Subject: [LARTC] Re: [PATCH 0/2] NET: Accurate packet scheduling for ATM/ADSL
Date: Tue, 27 Jun 2006 06:19:45 +0000 [thread overview]
Message-ID: <44A0CE01.4010109@stuart.id.au> (raw)
In-Reply-To: <449FC0AF.1050904@trash.net>
On 26/06/2006 9:10 PM, Patrick McHardy wrote:
>>5. We still did have to modify the kernel for ATM. That was
>> because of its rather unusual characteristics. However,
>> it you look at the size of modifications made to the kernel
>> verses the size made to the user space tool, (37 lines
>> versus 303 lines,) the bulk of the work was does in user
>> space.
>
> I'm sorry, but arguing that a limited special case solution is
> better because it needs slightly less code is just not reasonable.
Without seeing your actual proposal it is difficult to
judge whether this is a reasonable trade-off or not.
Hopefully we will see your code soon. Do you have any
idea when?
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-06-27 6:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1150278004.26181.35.camel@localhost.localdomain>
[not found] ` <1150286766.5233.15.camel@jzny2>
2006-06-14 15:32 ` [LARTC] Re: [PATCH 0/2] NET: Accurate packet scheduling for ATM/ADSL Andy Furniss
2006-06-20 0:54 ` Patrick McHardy
[not found] ` <1150815375.5270.78.camel@jzny2>
2006-06-20 15:09 ` Patrick McHardy
[not found] ` <1150289724.26181.74.camel@localhost.localdomain>
[not found] ` <1150377383.5116.38.camel@jzny2>
2006-06-20 1:04 ` Patrick McHardy
[not found] ` <1150815544.5270.82.camel@jzny2>
2006-06-20 15:16 ` Patrick McHardy
[not found] ` <1150287983.3246.27.camel@ras.pc.brisbane.lube>
[not found] ` <1150292693.5197.1.camel@jzny2>
[not found] ` <1150843471.17455.2.camel@ras.pc.brisbane.lube>
[not found] ` <15653CE98281AD4FBD7F70BCEE3666E53CD54A@comxexch01.comx.local>
[not found] ` <1151000966.5392.34.camel@jzny2>
2006-06-23 12:37 ` [LARTC] " Russell Stuart
[not found] ` <449C06E3.3090406@trash.net>
2006-06-26 0:45 ` [LARTC] " Russell Stuart
[not found] ` <449FC0AF.1050904@trash.net>
2006-06-27 6:19 ` Russell Stuart [this message]
[not found] ` <44AA6D25.9000707@trash.net>
2006-07-06 0:39 ` Russell Stuart
[not found] ` <44AE1497.6010904@trash.net>
2006-07-10 8:44 ` Russell Stuart
[not found] ` <1151158431.6716.95.camel@jzny2>
2006-06-26 4:23 ` Russell Stuart
2006-07-18 2:06 ` [LARTC] " Russell Stuart
[not found] ` <44BD56A4.9090002@andyfurniss.entadsl.com>
[not found] ` <1153270932.4242.60.camel@ras.pc.brisbane.lube>
[not found] ` <44BE46A6.8000207@trash.net>
2006-07-20 4:56 ` [LARTC] " Russell Stuart
2006-07-30 23:06 ` Russell Stuart
[not found] ` <44BE44E3.9080100@andyfurniss.entadsl.com>
[not found] ` <Pine.LNX.4.61.0607192114240.9570@tyr.diku.dk>
[not found] ` <20060719210004.GB20264@ms2.inr.ac.ru>
2006-07-20 5:47 ` [LARTC] Re: [PATCH 0/2] NET: Accurate packet scheduling for Russell Stuart
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=44A0CE01.4010109@stuart.id.au \
--to=russell@stuart.id.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hadi@cyberus.ca \
--cc=hawk@diku.dk \
--cc=kaber@trash.net \
--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