From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by wa-out-1112.google.com with SMTP id m33so5288497wag.8 for ; Thu, 20 Dec 2007 09:24:54 -0800 (PST) Message-ID: <6934efce0712200924o4e676484j95188a01b605bfdc@mail.gmail.com> Date: Thu, 20 Dec 2007 09:24:54 -0800 From: "Jared Hulbert" Subject: Re: [rfc][patch 2/2] xip: support non-struct page memory In-Reply-To: <476A8133.5050809@de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071214133817.GB28555@wotan.suse.de> <20071214134106.GC28555@wotan.suse.de> <476A73F0.4070704@de.ibm.com> <476A7D21.7070607@de.ibm.com> <476A8133.5050809@de.ibm.com> Sender: owner-linux-mm@kvack.org Return-Path: To: carsteno@de.ibm.com Cc: Nick Piggin , Linux Memory Management List , Martin Schwidefsky List-ID: > A poor man's solution could be, to store a pfn range of the flash chip > and/or shared memory segment inside vm_area_struct, and in case of > VM_MIXEDMAP we check if the pfn matches that range. If so: no > refcounting. If not: regular refcounting. Is that an option? I'm not picturing what is responsible for configuring this stored pfn range. Does the fs do it on mount? Does the MTD or your funky direct_access block driver do it? What if you use VM_PFNMAP instead of VM_MIXEDMAP? -- 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