* MAX_ORDER in mmzone.h
@ 2012-08-27 2:30 J.Hwan Kim
2012-08-27 5:25 ` Prabhakar Lad
0 siblings, 1 reply; 2+ messages in thread
From: J.Hwan Kim @ 2012-08-27 2:30 UTC (permalink / raw)
To: kernelnewbies
Hi, everyone
I wish to expand the limit for allocating contiguous memory in kernel.
So, if I change the value CONFIG_FORCE_MAX_ZONEORDER or
MAX_ORDER value in /include/linux/mmzone.h,
will it cause any problem or side effect in x86_64 sysem?
Thanks in advance.
Best Regards,
J.Hwan Kim
^ permalink raw reply [flat|nested] 2+ messages in thread
* MAX_ORDER in mmzone.h
2012-08-27 2:30 MAX_ORDER in mmzone.h J.Hwan Kim
@ 2012-08-27 5:25 ` Prabhakar Lad
0 siblings, 0 replies; 2+ messages in thread
From: Prabhakar Lad @ 2012-08-27 5:25 UTC (permalink / raw)
To: kernelnewbies
Hi,
On Mon, Aug 27, 2012 at 8:00 AM, J.Hwan Kim <frog1120@gmail.com> wrote:
> Hi, everyone
>
> I wish to expand the limit for allocating contiguous memory in kernel.
> So, if I change the value CONFIG_FORCE_MAX_ZONEORDER or
> MAX_ORDER value in /include/linux/mmzone.h,
> will it cause any problem or side effect in x86_64 sysem?
>
Recently Contiguous memory allocator got merged into 3.5 Kernel
you can use the same to declare as much contiguous memory needed.
Thx,
--Prabhakar Lad
http://www.linkedin.com/profile/view?id=65006993&trk=tab_pro
> Thanks in advance.
>
> Best Regards,
> J.Hwan Kim
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-08-27 5:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-08-27 2:30 MAX_ORDER in mmzone.h J.Hwan Kim
2012-08-27 5:25 ` Prabhakar Lad
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.