From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Regarding module size change in ARM kernel
Date: Wed, 16 Jul 2014 19:45:17 +0100 [thread overview]
Message-ID: <20140716184517.GR21766@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAKuQT6xdcsQM6a4PXO40SvbqSdccJ7bkS6Arz0yqU9RRpcoVQA@mail.gmail.com>
On Wed, Jul 16, 2014 at 05:51:16PM +0100, Venkateswar Rao Goli wrote:
> Hi there,
>
> I'm running out of module size memory i.e, 14MB ( CONFIG_HIGHMEM is
> enabled in config ) .
Quite simply, don't have such big modules. Really. If you're filling
14MB you're doing something very wrong.
> I've tried to increase by changing as below,
> could you please let us know if it would cause any regressions in any
> of the application or scenario ?
You're increasing the chances that the module text won't be able to reach
the kernel text, and so relocations will fail. 18MB should work fine
provided your kernel is no larger than 14MB.
But seriously, do something about your huge modules. Filling 14MB is
just insane.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2014-07-16 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 16:51 Regarding module size change in ARM kernel Venkateswar Rao Goli
2014-07-16 18:45 ` Russell King - ARM Linux [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140716184517.GR21766@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).