From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by ozlabs.org (Postfix) with ESMTP id 791F4DDE03 for ; Thu, 13 Dec 2007 06:19:38 +1100 (EST) To: Or Gerlitz Subject: Re: [ewg] Re: [PATCH] IB/ehca: Serialize HCA-related hCalls on POWER5 References: <475FD0A1.3090304@voltaire.com> From: Roland Dreier Date: Wed, 12 Dec 2007 11:09:27 -0800 In-Reply-To: <475FD0A1.3090304@voltaire.com> (Or Gerlitz's message of "Wed, 12 Dec 2007 14:14:25 +0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Arnd Bergmann , Joachim Fenkes , LKML , linuxppc-dev@ozlabs.org, Christoph Raisch , OF-General , Stefan Roscher List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > What is the fix you suggest, to add a device query that tells you for > which verbs the documentation does not apply? or enhance the code of the > map_phys_fmr verb within the ehca driver to return error if called > from non-sleepable context? I think the right fix for iSER would be to make iSER work even for devices that don't support FMRs. For example cxgb3 doesn't implement FMRs so if anyone ever updates iSER to work on iWARP and not just IB, then this is something that has to be tackled anyway. Then ehca could just get rid of the FMR support it has.