From: Mike Mestnik <cheako911@yahoo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Modems: Cable or DSL digital blunders that lartc may help with.
Date: Wed, 23 Jun 2004 04:19:29 +0000 [thread overview]
Message-ID: <20040623041929.27977.qmail@web11903.mail.yahoo.com> (raw)
In-Reply-To: <20040622043359.75922.qmail@web11905.mail.yahoo.com>
--- Ed Wildgoose <lists@wildgooses.com> wrote:
>
> >http://www.lammertbies.nl/comm/info/RS-232_flow_control.html
> >ECN is software flow control. There is also icmp for software FC? The
> >idea is too prevent 'buffer underruns' in the modem, any SNMP or other
> >stats on this buffer would also provide SWFC.
> >
> >
>
> I don't consider this to be "flow-control" in the sense of throttling
> sending. This is really a syncronisation protocol.
>
Yes, SwFC is lame. Howerver it would be a good band-aid, to have router
and modem syncronisation take place.
> >http://www.nwfusion.com/netresources/0913flow.html
> >This is ethernets HWFC, that any directly connected modem could use.
> The
> >idea then is for the directly connected computer to use SwFC(ECN or
> >?icmp?) to pass this FC onto other hosts using the modem.
> >
> >
>
> Hmm, I wasn't aware of a "pause" ability for ethernet. But still this
> is a very low level layer 1 protocol. In other words this will calm
> your 100mb net card talking to your 10mbit port on your cable modem.
> But it has no idea that the cable modem only has a 256kb link
>
The router(PC) has no idea of the buffer fullness, this is the underlying
problem! The cable modem needs to triger a "pause" when it's buffer
reaches %80 full, regardless of any other rate limiting. Linux kernel can
do this with some cards, under heavy CPU strain(htb).
CONFIG_NET_HW_FLOWCONTROL: net/Kconfig
> You need something which works at IP level or above. TCP (level higher)
>
No, the DEVICE is not > layer 3. It's simply a bridge, with a stoplight
on one end. The idea is to not make any cars crash, that has nothing todo
with the ball game a car might want to get too.
> has some stuff, but (I repeat) it basically involves dropping traffic
> until the sender slows down. There are protocols like ECN, but they are
>
Yes, ECN will/should be used for routers attached to bridges.
> broadly unsupported. ICMP stuff is frequently dropped by
> routers/firewalls making it problematic (look at how difficult it is
> just to do MTU discovery!)
>
ECN makes this a non-issue.
> What's your question though? Read the LARTC howto and the ADSL QOS
> howto. They are both excellent docs. Also read up on some basic TCP
> notes. There is nothing really clever that you can do - it's all in the
>
> docs you just have to work around the limitations of the protocols
>
I would like to know is maby a ?$6000.00? Cisco cable mobem will not only
use HwFC but ECN as well? Thought i'd like to find a $150.00 modem that
will just do HwFC, maby an internal one?
> Ed W
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-23 4:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 4:33 [LARTC] Modems: Cable or DSL digital blunders that lartc may help with Mike Mestnik
2004-06-22 4:55 ` Jason Boxman
2004-06-22 9:29 ` [LARTC] Modems: Cable or DSL digital blunders that lartc may Ed Wildgoose
2004-06-22 16:44 ` [LARTC] Modems: Cable or DSL digital blunders that lartc may help with Mike Mestnik
2004-06-22 21:50 ` [LARTC] Modems: Cable or DSL digital blunders that lartc may Ed Wildgoose
2004-06-23 4:19 ` Mike Mestnik [this message]
2004-06-23 8:15 ` Ed Wildgoose
2004-06-23 15:37 ` [LARTC] Modems: Cable or DSL digital blunders that lartc may help with Mike Mestnik
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=20040623041929.27977.qmail@web11903.mail.yahoo.com \
--to=cheako911@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox