From mboxrd@z Thu Jan 1 00:00:00 1970 From: saeed bishara Subject: Re: Highmem issues with MMC filesystem Date: Thu, 18 Mar 2010 15:42:25 +0200 Message-ID: References: <037201cac5d7$6c5b8c60$LocalHost@wipblrx0099946> <043e01cac5df$c3ec1b90$LocalHost@wipblrx0099946> <20100318092352.GD8267@n2100.arm.linux.org.uk> <20100318112453.GA19544@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-yx0-f182.google.com ([209.85.210.182]:54459 "EHLO mail-yx0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753474Ab0CRNm0 (ORCPT ); Thu, 18 Mar 2010 09:42:26 -0400 Received: by yxe12 with SMTP id 12so52142yxe.33 for ; Thu, 18 Mar 2010 06:42:25 -0700 (PDT) In-Reply-To: <20100318112453.GA19544@n2100.arm.linux.org.uk> Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Russell King - ARM Linux Cc: Nicolas Pitre , Hemanth V , linux-mmc@vger.kernel.org, pierre@ossman.eu, linux-arm-kernel@lists.infradead.org > In no case does the kernel ever clean user space cache lines for DMA; > that's not the responsibility of the DMA API. I understand that it's not the DMA API's responsibility to flush user space cache lines, but other parts of the kernel should do that right? otherwise DIRECT_IO won't work (though the issue here has nothing to do with DIRECT_IO). saeed