From mboxrd@z Thu Jan 1 00:00:00 1970 From: jamal Subject: Re: netif_rx packet dumping Date: 03 Mar 2005 17:26:51 -0500 Message-ID: <1109888811.1092.352.camel@jzny.localdomain> References: <20050303123811.4d934249@dxpl.pdx.osdl.net> <20050303125556.6850cfe5.davem@davemloft.net> <1109884688.1090.282.camel@jzny.localdomain> <20050303132143.7eef517c@dxpl.pdx.osdl.net> <1109885065.1098.285.camel@jzny.localdomain> <20050303133237.5d64578f.davem@davemloft.net> <20050303135416.0d6e7708@dxpl.pdx.osdl.net> Reply-To: hadi@cyberus.ca Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Stephen Hemminger , "David S. Miller" , rhee@eos.ncsu.edu, Yee-Ting.Li@nuim.ie, baruch@ev-en.org, netdev@oss.sgi.com To: John Heffner In-Reply-To: Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org On Thu, 2005-03-03 at 17:02, John Heffner wrote: > On Thu, 3 Mar 2005, Stephen Hemminger wrote: > > Maybe a simple Random Exponential Drop (RED) would be more friendly. > > That would probably not be appropriate. This queue is only for absorbing > micro-scale bursts. It should not hold any data in steady state like a > router queue can. The receive window can handle the macro scale flow > control. recall this is a queue that is potentially shared by many many flows from potentially many many interfaces i.e it deals with many many micro-scale bursts. Clearly, the best approach is to have lots and lots of memmory and to make that queue real huge so it can cope with all of them all the time. We dont have that luxury - If you restrict the queue size, you will have to drop packets... Which ones? Probably simplest solution is to leave it as is right now and just adjust the contraints based on your system memmory etc. cheers, jamal