From owner-freebsd-arch@FreeBSD.ORG Sun Jan 21 23:02:33 2007 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A8E1B16A403 for ; Sun, 21 Jan 2007 23:02:33 +0000 (UTC) (envelope-from marius.nuennerich@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id ECB6913C45B for ; Sun, 21 Jan 2007 23:02:32 +0000 (UTC) (envelope-from marius.nuennerich@gmx.net) Received: (qmail invoked by alias); 21 Jan 2007 22:35:52 -0000 Received: from dslb-084-061-193-105.pools.arcor-ip.net (EHLO sol.hackerzberg.local) [84.61.193.105] by mail.gmx.net (mp027) with SMTP; 21 Jan 2007 23:35:52 +0100 X-Authenticated: #5707313 Date: Sun, 21 Jan 2007 23:35:45 +0100 From: Marius Nuennerich To: freebsd-arch@freebsd.org Message-ID: <20070121233545.2a8ce09a@sol.hackerzberg.local> In-Reply-To: References: <20070121140019.A83688@xorpc.icir.org> X-Mailer: Claws Mail 2.7.0 (GTK+ 2.10.7; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: bzero & bcopy alignment X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2007 23:02:33 -0000 On Sun, 21 Jan 2007 23:25:14 +0100 Ivan Voras wrote: > Luigi Rizzo wrote: > > On Sun, Jan 21, 2007 at 10:41:09PM +0100, Ivan Voras wrote: > >> Following recent discussion on alignment of bzero() and bcopy(), I've > >> added some statistics collecting code to bzero() and bcopy() for > >> practice (on a RELENG_6 box), and here are the cumulative results for > >> argument alignment: > > > > i think these profiles depend heavily on the hardware > > and usage patterns. > > Yes, I agree. For what it's worth, this was on vmware, almost no network > activity. > > > e.g. some network drivers force you to aligned buffers > > which results in misaligned payload requesting in > > turn an unaligned bcopy. Not that one can help with this, > > but i think that is also important to locate the locations > > in the source where the poorly aligned (1-2, maybe > > 4 and 8 to some degree) ops occur. > > Any magic tricks to identify the caller of "current" function in the kernel? I don't know if the dtrace port is ready for this, but afaik it would be easy with dtrace.