lkml.org 
[lkml]   [2002]   [Nov]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] modules as shared objects
On Sat, Nov 23, 2002 at 05:16:32PM -0800, Adam J. Richter wrote:
> I was wondering if there is any other ultimate benefit to your change.

I think the main benefit is leaving some of the hard bits
wrt linking to the user-space linker. Doesn't affect x86,
but it does affect at least alpha and ia64.

> So, if you adopt a policy that the .init section will be loaded
> contiguously ...

Well, due to the way shared libraries are constructed, the
.init sections *must* be loaded contiguously no matter what.
The question is, how to free that memory.

> I should also check and see if kmalloc returns pointers in the 4MB
> kernel huge page on x86, which would improve TLB usage.

I believe it does. This decision must be left to the per-arch
allocation routine though.


r~
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:31    [W:0.025 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site