mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Satchell <list@fluent2.pyramid.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	dirk@staf.planetinternet.be (Dirk Moerenhout)
Cc: jeffm@iglou.com (Jeff Mcadams), linux-kernel@vger.kernel.org
Subject: Re: Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.hel
Date: Sat, 22 Dec 2001 08:10:25 -0800	[thread overview]
Message-ID: <4.3.2.7.2.20011222080457.00be8100@10.1.1.42> (raw)
In-Reply-To: <E16HnxA-0004SS-00@the-village.bc.nu>
In-Reply-To: <Pine.LNX.4.33.0112221538560.214-100000@dirk>

At 03:20 PM 12/22/01 +0000, Alan Cox wrote:
>It gets worse the deeper you go. Over an HDLC based link for example
>sequences of five one bits take longer to send due to bitstuffing. Any
>networking terminology is generally grossly simplified.

Interestingly, the subject of bit-stuffing came up during the discussion of 
modem testing, because of the HDLC framing used in V.42 error 
control.  Statistics provided by the representative from Hayes (R.I.P.) 
showed that bit-stuffing occurred in roughly 1 out of 64 bits in the data 
path when V.42 bis data compression was enabled.  The 1:63 ratio held over 
a surprisingly wide range of data patterns, all the way from repeated 
single characters through text in English, French, German, and Chinese to 
the output of a 64-bit random number generator.  When v.42 bis data 
compression was disabled, the average ratio was about the same but there 
was considerably more spread because of data pattern sensitivity.

Which is grossly off-topic but I thought a few of you might be interested.

Stephen Satchell


  parent reply	other threads:[~2001-12-22 16:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-20 18:36 Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.hel p Dana Lacoste
2001-12-20 19:13 ` Nicholas Knight
2001-12-20 19:41   ` Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.help Mike Harrold
2001-12-21 16:59     ` Alan Cox
2001-12-21 17:50       ` Mike Harrold
2001-12-21 18:41         ` Kent Borg
2001-12-21 18:49           ` lk
2001-12-21 19:12             ` Kent Borg
2001-12-22  4:51         ` Albert D. Cahalan
2001-12-20 19:43   ` Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.hel p David Weinehall
2001-12-20 23:12     ` [OT] " Wilfried Weissmann
2001-12-20 23:13       ` Nicholas Knight
2001-12-20 23:03 ` ncw
2001-12-22  7:52   ` Mikael Abrahamsson
2001-12-22 12:53     ` Jeff Mcadams
2001-12-22 15:03       ` Dirk Moerenhout
2001-12-22 15:20         ` Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.hel Alan Cox
2001-12-22 16:10         ` Stephen Satchell [this message]
2001-12-22 17:43         ` Changing KB, MB, and GB to KiB, MiB, and GiB in Configure.hel p mirabilos {Thorsten Glaser}
2001-12-22 22:21           ` Vojtech Pavlik

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=4.3.2.7.2.20011222080457.00be8100@10.1.1.42 \
    --to=list@fluent2.pyramid.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dirk@staf.planetinternet.be \
    --cc=jeffm@iglou.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®