RE: discussion of buffers

2001-03-08 Thread Greg Owens

http://www.cisco.com/warp/public/650/41.html



http://www.cisco.com/warp/public/63/buffertuning.html

http://www.cisco.com/warp/public/63/bufferleak_troubleshooting.html



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
george
Sent: Thursday, March 08, 2001 8:35 PM
To: [EMAIL PROTECTED]
Subject: discussion of buffers

Anyone have good a good refrence on cisco routers and their use of buffers,
including discussions on optimizing their size?


_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: discussion of buffers

2001-03-08 Thread Howard C. Berkowitz

Anyone have good a good refrence on cisco routers and their use of buffers,
including discussions on optimizing their size?


The IOS internals book (sorry, I'm blanking on the exact title) has a 
detailed discussion of buffering.

As far as optimizing them, however, my best advice is:

1.  Leave them alone unless there appears to be a problem.  Precise
details of buffer handling are release- and platform-dependent.
In any case, a great deal of effort is expended in ANY modern
operating system to have buffer management be self-tuning.

2.  If there does appear to be a problem, involve the TAC. Figuring
out what's needed may very well need to involve someone with
code access.

I've rarely needed to tune buffers, certainly in recent IOS releases. 
About the only general rule I could suggest is when forcing a WAN 
interface into process switching to get more buffers or per-packet 
load balancing, be sure the buffer pool can hold a full window (of 
whatever windowing protocols you are using).

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]