[lkml]   [2006]   [Dec]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] [PATCH] virtual memmap on sparsemem v3 [1/4] map and unmap
On Fri, 8 Dec 2006 16:28:19 -0800
Andrew Morton <> wrote:

> Generally we prefer to simply *require* that the function vector be filled
> in appropriately. So if the caller has no special needs, the caller will
> set their gen_map_kern_ops.k_pte_alloc to point at pte_alloc_kernel().
> erk, pte_alloc_kernel() is a macro. As is pmd_alloc(), etc. Well, let
> that be a lesson to us. What a mess.
> I suppose we could go through and convert them all to inlines and then the
> compiler will generate an out-of-line copy for us. Better would be to turn
> these things into regular, out-of-line C functions.
> What a mess.

Thank you for review. I'll remove this default action.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-12-09 03:43    [W:0.057 / U:4.584 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site