HP3000-L Archives

August 2009, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Mon, 17 Aug 2009 16:30:32 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Hoxsie, Howard wrote:
> Years ago I was told that it is also helpful to keep the HP3K on its own
> sub-net.  Something about much fewer interrupts to throw away?

Extremely true for shared, half-duplex networks and hubs, from the
coax-tapping or other shared media days.

Still a valid concern for today's networks, from both a performance and
security perspective.

But with modern switches supporting multiple virtual LANs or even
virtual networks (VRFs), many still operate with a shared buffer pool. 
The availability of those buffers is dependent on the aggregate amount
of traffic traversing the switch, regardless of subnet / vlan / vrf.

There are also switches with fixed buffer allocations, or their own pool
management to avoid exhaustion.  Just another detail that seldom rears
it's ugly head until you approach one of the design limits of the device.

If you want to avoid all those constraints, find a switch that provides
true non-blocking, wire-speed forwarding.  They are few, and they are
expensive.

Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2