From: Jack W. Williams (jack.w.williams@xxxxxxxx)
Date: Mon Jan 07 2002 - 14:53:22 GMT-3
When I told my employers we didn't have to worry about Y2K for 48 more years
they didn't think it was very funny.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Wade Edwards
Sent: Monday, January 07, 2002 10:34 AM
To: Brown, Nelson; ccielab@groupstudy.com
Subject: RE: 1000 vs 1024?
When you are talking about memory then 1K = 1024. When you are talking
about hard drive space then 1K = 1024 (although hard drive manufactures
quote their drive sizes as 1K = 1000 this is just marketing.) When you
are talking about bandwidth 1K = 1000. This is the way the
telecommunications industry does it.
L8r.
-----Original Message-----
From: Brown, Nelson [mailto:Nelson.Brown@NASD.com]
Sent: Monday, January 07, 2002 10:49 AM
To: ccielab@groupstudy.com
Subject: RE: 1000 vs 1024?
For all telecom and networking apps, 1k = 1000, not 1024.
-----Original Message-----
From: Waters, Kivas (UK72) [mailto:Kivas.Waters@Honeywell.com]
Sent: Saturday, January 05, 2002 10:21 AM
To: ccielab@groupstudy.com
Subject: 1000 vs 1024?
Can someone advise me when translating kilo-bit values to byte values
and
vica versa.
In some lab scenario model answers there appears to me to be some
inconsistency when it comes to configuring FR broadcast traffic shaping
for
example. Here's an example :
You are asked to reduce the effect of broadcast traffic flooding a FR
serial
link (S0). You are given the following parameters : Q size of 80 ; 300
kbps
broadcast data rate ; 200 packets per second.
The solution needs : frame-relay broadcast-queue <Qsize> <bytes/sec>
<packets/sec>
My question is, how do I interpret the 300 kbps? Is it (300*1024)/8 or
(300*1000)/8?
This is my guess ...
frame-relay broadcast-queue 80 38400 200
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:19 GMT-3