From owner-freebsd-hackers Tue Jun 3 21:10:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA18763 for hackers-outgoing; Tue, 3 Jun 1997 21:10:13 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA18758 for ; Tue, 3 Jun 1997 21:10:10 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA11449; Wed, 4 Jun 1997 13:39:21 +0930 (CST) From: Michael Smith Message-Id: <199706040409.NAA11449@genesis.atrad.adelaide.edu.au> Subject: Re: Need help with fastest way to move data... In-Reply-To: <199706040229.WAA21318@spoon.beta.com> from "Brian J. McGovern" at "Jun 3, 97 10:29:06 pm" To: mcgovern@spoon.beta.com (Brian J. McGovern) Date: Wed, 4 Jun 1997 13:39:20 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian J. McGovern stands accused of saying: > > Now, the big question... Is this the most efficient way to do this? > Does memcpy and the like work best on long-aligned values. Would it > be even MORE efficient to use larger structures, given sufficient > data to move? The best way to go is : - establish the largest linear chunk you can move. - call bcopy to move it. - repeat until done. > I'm curious to hear comments, and see if anyone has any truely cool ideas. Leave worrying about alignment etc. to the primitives; the moment you leave the original platform everything is going to change anyway. > -Brian -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[