Thanks very much. So confirm, there is nothing that says one PIC will get
a certain amount at minimum right?
What determines what is dropped when there is contention on the bus? Are
there any commands I could use to see whether a bus is/was congested and
how much of what was dropped?
On Sat,
If you oversubscribe the bus you oversubscribe the bus. Traffic load
v.s. average packet size v.s. level of oversubscrip v.s. burstiness will
determine loss potential.
On 2/26/13 11:59 AM, Matt Bentley wrote:
Thanks very much. So confirm, there is nothing that says one PIC will
get a certain
OK - so there has been a lot of discussion around this that I've seen, but
I've searched for hours and still can't find concrete answers. Can someone
help?
1. Does the 3.2 Gbps throughput limitation include overhead? In other
words, Is the raw throughput 4 Gbps with effective throughput of 3.2
With the std cfeb after internal overhead per bus capacity is 3.2Gbit of
traffic, this is worst case minimum small packets, etc.
Raw bus capacity is IIRC ~ 4Gbit, difference is overhead.
Unless you are doing all small packet, actual limit is higher than 3.2.
Enhanced CFEB bumps the raw bus
Thanks! So it would be correct to say you should NEVER see
oversubscription on a channelized DS3 card right? Obviously, you can
overdrive a single T1, but you'd never see drops due to the PIC itself? I
guess what I'm asking is whether or not the bandwidth availalble on a FPC
is allocated
Bus is _shared_, with CFEB you have guaranteed 3.2Gbit shared by up to 4
PICs, with E-CFEB is non issue single PIC limit is 1G and E-CFEB will do
full 1G per no matter what.
If you try to handle more than 3.2Gbit on a CFEB bus (X-0/X/X or
X-1/X/X) you may see bus contention depending on packet
6 matches
Mail list logo
