From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: patch for common networking error messages Date: Tue, 17 Jun 2003 15:23:09 -0400 Sender: linux-kernel-owner@vger.kernel.org Message-ID: <3EEF6A9D.6050303@pobox.com> References: <200306170434.h5H4YZPZ003025@turing-police.cc.vt.edu> <20030617090859.0ffa0ca8.shemminger@osdl.org> <20030617.090930.102574393.davem@redhat.com> <3EEF620A.40608@pobox.com> <3EEF66AA.3000509@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: "David S. Miller" , shemminger@osdl.org, Valdis.Kletnieks@vt.edu, Janice Girouard , Daniel Stekloff , Larry Kessler , linux-kernel@vger.kernel.org, netdev@oss.sgi.com, niv@us.ibm.com Return-path: To: Janice M Girouard In-Reply-To: <3EEF66AA.3000509@us.ibm.com> List-Id: netdev.vger.kernel.org Janice M Girouard wrote: > 2) events that drive load balancing software. Right now if we need to > throttle the card, we don't send events up to indicate we have reached > capacity. Question related to this item specifically :) Do you want to individually send 4000 - 16000 (or more) TX stop / start events per second to userspace? :) At some point Heisenburg defeats low latency :) If not (and I hope not), perhaps also look into the net stack statistics already kept (or add more sampling stats if necessary), and instead trigger events based on sampling those statistics. Jeff