From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751451AbWGLQP4 (ORCPT ); Wed, 12 Jul 2006 12:15:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751452AbWGLQP4 (ORCPT ); Wed, 12 Jul 2006 12:15:56 -0400 Received: from mx2.suse.de ([195.135.220.15]:63158 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S1751451AbWGLQPz (ORCPT ); Wed, 12 Jul 2006 12:15:55 -0400 To: "Bryan O'Sullivan" Cc: davem@davemloft.net, arjan@infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Add memcpy_cachebypass, a copy routine that tries to keep cache pressure down References: From: Andi Kleen Date: 12 Jul 2006 18:15:45 +0200 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Bryan O'Sullivan writes: > + * memcpy_cachebypass - memcpy-compatible copy routine, using streaming loads > + * @dest: destination address > + * @src: source address (will not be cached) > + * @count: number of bytes to copy > + * > + * Use streaming loads and normal stores for a special-case copy where > + * we know we won't be reading the source again, but will be reading the > + * destination again soon. > + */ For what CPU did you optimize that function? Comment missing for that. Also the comment should state that you're caching the target. Also I trust you ran it through a comprehensive memcpy-all-cases tester? -Andi