From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751881AbaCVWYJ (ORCPT ); Sat, 22 Mar 2014 18:24:09 -0400 Received: from gw-1.arm.linux.org.uk ([78.32.30.217]:35451 "EHLO pandora.arm.linux.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750831AbaCVWXp (ORCPT ); Sat, 22 Mar 2014 18:23:45 -0400 Date: Sat, 22 Mar 2014 22:23:06 +0000 From: Russell King - ARM Linux To: James Bottomley Cc: Laura Abbott , Fenghua Yu , Tony Luck , Andrew Morton , linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org, Benjamin Herrenschmidt , x86@kernel.org, Heiko Carstens , linux-kernel@vger.kernel.org, linux390@de.ibm.com, sparclinux@vger.kernel.org, Ingo Molnar , Paul Mackerras , "H. Peter Anvin" , Martin Schwidefsky , linux-ia64@vger.kernel.org, Thomas Gleixner , linuxppc-dev@lists.ozlabs.org, "David S. Miller" , linux-arm-kernel@lists.infradead.org Subject: Re: [RESEND][PATCH 1/2] lib/scatterlist: Make ARCH_HAS_SG_CHAIN an actual Kconfig Message-ID: <20140322222306.GM7528@n2100.arm.linux.org.uk> References: <1395512032-20575-1-git-send-email-lauraa@codeaurora.org> <1395512032-20575-2-git-send-email-lauraa@codeaurora.org> <1395523881.2143.58.camel@dabdike.int.hansenpartnership.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1395523881.2143.58.camel@dabdike.int.hansenpartnership.com> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 22, 2014 at 02:31:21PM -0700, James Bottomley wrote: > Perhaps now might be the time to ask which are the remaining > architectures that cannot do SG chaining and then we can fix them and > pull the whole thing out. Not quite. You're making the assumption that we can be sure that all the scatterlist users on an architecture have been converted - that's simply not true on ARM. We have some which have, and some which still have not been audited. The cases that get us here would be old platform DMA code which walks scatterlists handed to it from drivers - stuff like arch/arm/mach-rpc/dma.c (which probably can cope), and drivers/scsi/arm/* (which definitely can't because of their SCSI pointers save/restore handling message.) I know that's one case where SG_CHAIN definitely isn't supported on ARM. So, we had decided not to enable it, but this means that new stuff isn't benefitting from this. I've recently asked arm-soc to enable it for the modern multi-platform builds, because modern stuff really be written with correct SG chaining in mind. -- FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly improving, and getting towards what was expected from it.