From owner-freebsd-hackers Thu Feb 25 6:35:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id C9E6314D8E for ; Thu, 25 Feb 1999 06:35:28 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.2/8.9.1) with ESMTP id JAA48676; Thu, 25 Feb 1999 09:34:53 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199902251434.JAA48676@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wes Peters Cc: dyson@iquest.net, Warner Losh , vincef@penmax.com, dennis@etinc.com, hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: cdrom.com bandwidth limits References: <199902231921.OAA03755@y.dyson.net> <36D3A26A.922CE5A9@softweyr.com> In-reply-to: Your message of "Tue, 23 Feb 1999 23:55:38 MST." <36D3A26A.922CE5A9@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Feb 1999 09:34:53 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "John S. Dyson" wrote: > > > > It is not likely to get that much due to protocol overheads, but I > > have seen >160KBytes/sec on a good T1. Don't T1's do bit stealing > > for signalling (I forget?) > > Unless you are on a "clear channel." If you are, the throughput is > 24 x 64 Kbits/sec, if not, 24 x 64 Kbits/sec - 8 Kbits/sec. The bit > stealing totals 8 Kbits/sec for the entire channel, regardless of how > "big" the channel is. Some CSU/DSU's can be pretty stupid when framing the synchronous data coming in for transmission on the T1 span. The problem they face is that there is a specific one's density requirement when pushing bits over the wire; if you have too many zero bits in a row, then the T1 span will blow it's clocking. So, some really stupid CSU/DSU's will format the data where they "force" every 8th bit to a one. This is how you end up with 1344 kb/s of bandwidth. The other more common way to do this is to observe that most modern uses of T1 spans for data transmission use HDLC bit-synchronous framing these days. If the DSU inverts the data coming in, then the HDCL framing will ensure adequate one's density on the T1 span. In this instance, you get to use all 1536 kb/s of capacity (64kb/s*24 channels) of the T1 span. The 1544 kb/s number you see including the T1 frame overhead, and isn't normally available if you expect to push your bits though a transmission system with other multiplexing equipment (M31 muxes, digital cross connect systems, etc.) louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message