Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 23 Aug 2002 20:07:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 23 Aug 2002 20:07:05 -0400 Received: from pizda.ninka.net ([216.101.162.242]:4511 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Fri, 23 Aug 2002 20:07:05 -0400 Date: Fri, 23 Aug 2002 16:55:46 -0700 (PDT) Message-Id: <20020823.165546.40701755.davem@redhat.com> To: manand@us.ibm.com Cc: alan@lxorguk.ukuu.org.uk, bcrl@redhat.com, bhartner@us.ibm.com, haveblue@us.ibm.com, linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net, lse-tech-admin@lists.sourceforge.net Subject: Re: [Lse-tech] Re: (RFC): SKB Initialization From: "David S. Miller" In-Reply-To: References: X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 774 Lines: 19 From: "Mala Anand" Date: Fri, 23 Aug 2002 18:38:59 -0500 To name a few, interrupts are disabled when skbs are put back to the hot_list A few cycles, at best, it should not be enough to skew the profiling and when the cache list is accessed in the slab allocator. Am I missing something? Please help me to understand. Which means if this were enough to skew profiling, it would make the program counter of the interrupt enable instruction in the SLAB code show up clearly in the profiles. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/