From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f52.google.com (mail-pb0-f52.google.com [209.85.160.52]) by kanga.kvack.org (Postfix) with ESMTP id 7374A6B0082 for ; Wed, 16 Apr 2014 15:03:49 -0400 (EDT) Received: by mail-pb0-f52.google.com with SMTP id rr13so11225461pbb.39 for ; Wed, 16 Apr 2014 12:03:49 -0700 (PDT) Received: from smtp.codeaurora.org (smtp.codeaurora.org. [198.145.11.231]) by mx.google.com with ESMTPS id pb4si13207171pac.154.2014.04.16.12.03.47 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Apr 2014 12:03:48 -0700 (PDT) Message-ID: <534ED412.1040909@codeaurora.org> Date: Wed, 16 Apr 2014 12:03:46 -0700 From: Laura Abbott MIME-Version: 1.0 Subject: Re: kmalloc and uncached memory References: <534ECCEB.6090007@codeaurora.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Lin Ming Cc: Peter Zijlstra , linux-mm , "linux-arm-kernel@lists.infradead.org" On 4/16/2014 11:50 AM, Lin Ming wrote: > On Wed, Apr 16, 2014 at 11:33 AM, Laura Abbott wrote: >> On 4/16/2014 11:11 AM, Lin Ming wrote: >>> Hi Peter, >>> >>> I have a performance problem(on ARM board) that cpu is very bus at >>> cache invalidation. >>> So I'm trying to alloc an uncached memory to eliminate cache invalidation. >>> >>> But I also have problem with dma_alloc_coherent(). >>> If I don't use dma_alloc_coherent(), is it OK to use below code to >>> alloc uncached memory? >>> >>> struct page *page; >>> pgd_t *pgd; >>> pud_t *pud; >>> pmd_t *pmd; >>> pte_t *pte; >>> void *cpu_addr; >>> dma_addr_t dma_addr; >>> unsigned int vaddr; >>> >>> cpu_addr = kmalloc(PAGE_SIZE, GFP_KERNEL); >>> dma_addr = pci_map_single(NULL, cpu_addr, PAGE_SIZE, (int)DMA_FROM_DEVICE); >>> vaddr = (unsigned int)uncached->cpu_addr; >>> pgd = pgd_offset_k(vaddr); >>> pud = pud_offset(pgd, vaddr); >>> pmd = pmd_offset(pud, vaddr); >>> pte = pte_offset_kernel(pmd, vaddr); >>> page = virt_to_page(vaddr); >>> set_pte_ext(pte, mk_pte(page, pgprot_dmacoherent(pgprot_kernel)), 0); >>> >>> /* This kmalloc memory won't be freed */ >>> >> >> No, that will not work. lowmem pages are mapped with 1MB sections underneath >> which cannot be (easily) changed at runtime. You really want to be using >> dma_alloc_coherent here. > > For "lowmem pages", do you mean the first 16M physical memory? > How about that if I only use highmem pages(>16M)? > By lowmem pages I am referring to the direct mapped kernel area. Highmem refers to pages which do not have a permanent mapping in the kernel address space. If you are calling kmalloc with GFP_KERNEL you will be getting a page from the lowmem region. What's the reason you can't use dma_alloc_coherent? Thanks, Laura -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org