Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759996Ab0FQNMZ (ORCPT ); Thu, 17 Jun 2010 09:12:25 -0400 Received: from cantor2.suse.de ([195.135.220.15]:55303 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759969Ab0FQNMX (ORCPT ); Thu, 17 Jun 2010 09:12:23 -0400 Subject: Re: bnx2 fails to compile on parisc because of missing get_dma_ops() From: James Bottomley To: Michael Chan Cc: "'FUJITA Tomonori'" , "vapier@gentoo.org" , "netdev@vger.kernel.org" , "linux-parisc@vger.kernel.org" , "linux-kernel@vger.kernel.org" In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Thu, 17 Jun 2010 08:12:16 -0500 Message-ID: <1276780336.2789.6.camel@mulgrave.site> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1562 Lines: 40 On Thu, 2010-06-17 at 05:54 -0700, Michael Chan wrote: > FUJITA Tomonori wrote: > > > From: FUJITA Tomonori > > Date: Thu, 17 Jun 2010 13:06:15 +0900 > > Subject: [PATCH] bnx2: fix dma_get_ops compilation breakage > > > > This removes dma_get_ops() prefetch optimization in bnx2. > > > > bnx2 uses dma_get_ops() to see if dma_sync_single_for_cpu() is > > noop. bnx2 does prefetch if it's noop. > > > > But dma_get_ops() isn't available on all the architectures (only the > > architectures that uses dma_map_ops struct have it). Using > > dma_get_ops() in drivers leads to compilation breakage on many > > archtectures. > > > > Currently, we don't have a way to see if dma_sync_single_for_cpu() is > > noop. If it can improve the performance notably, we can add the new > > DMA API for it. > > This prefetch improves performance noticeably when the driver is > handling incoming 64-byte packets at a sustained rate. So why not do it unconditionally? The worst that can happen is that you pull in a stale cache line which will get cleaned in the dma_sync, thus slightly degrading performance on incoherent architectures. Alternatively, come up with a dma prefetch infrastructure ... all you're really doing is hinting to the architecture that you'll sync this region next. James -- 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/