Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758181Ab0FQBQW (ORCPT ); Wed, 16 Jun 2010 21:16:22 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:53505 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754847Ab0FQBQU (ORCPT ); Wed, 16 Jun 2010 21:16:20 -0400 Date: Wed, 16 Jun 2010 18:16:32 -0700 (PDT) Message-Id: <20100616.181632.27807395.davem@davemloft.net> To: JBottomley@Novell.com Cc: netdev@vger.kernel.org, linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp, mchan@broadcom.com Subject: Re: bnx2 fails to compile on parisc because of missing get_dma_ops() From: David Miller In-Reply-To: <1276737229.2847.853.camel@mulgrave.site> References: <1276737229.2847.853.camel@mulgrave.site> X-Mailer: Mew version 6.3 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1156 Lines: 35 From: James Bottomley Date: Wed, 16 Jun 2010 20:13:49 -0500 > However, this code in bnx2.c: > > if (!get_dma_ops(&pdev->dev)->sync_single_for_cpu) { > next_rx_buf = > &rxr->rx_buf_ring[ > RX_RING_IDX(NEXT_RX_BD(sw_cons))]; > prefetch(next_rx_buf->desc); > } > > Looks remarkably fragile: what exactly is it trying to do? > > The commit that causes the problem: > > commit a33fa66bcf365ffe5b79d1ae1d3582cc261ae56e > Author: Michael Chan > Date: Thu May 6 08:58:13 2010 +0000 > > bnx2: Add prefetches to rx path. > > Looks fairly innocuous by the description. > > Should parisc have a get_dma_ops()? We don't need one because our dma > ops are per platform not per bus. I think asking for get_dma_ops() directly in a driver is dodgy at best, especially one that is meant to compile on any PCI supporting system. At least right now. -- 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/