From: Ralf Baechle <ralf@linux-mips.org>
To: moreau francis <francis_moreau2000@yahoo.fr>
Cc: linux-mips@linux-mips.org
Subject: Re: Re : module allocation
Date: Tue, 2 May 2006 10:36:21 +0100 [thread overview]
Message-ID: <20060502093621.GA4301@linux-mips.org> (raw)
In-Reply-To: <20060502071949.44638.qmail@web25811.mail.ukl.yahoo.com>
On Tue, May 02, 2006 at 07:19:49AM +0000, moreau francis wrote:
> > There is another reason against putting modules into mapped space and
> > that's the need for -mlong-calls which generates larger, less efficient
> > code.
>
> BTW, I don't see why -mlong-calls wouldn't be needed for GFP module
> allocation. Can you explain ?
It assumes a low-memory system where the entire RAM resides within the
range of a J/JAL instructions.
Ralf
next prev parent reply other threads:[~2006-05-02 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 13:04 module allocation moreau francis
2006-04-28 20:03 ` Ralf Baechle
2006-05-02 7:19 ` Re : " moreau francis
2006-05-02 9:36 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-29 9:41 moreau francis
2006-04-29 20:39 ` Ralf Baechle
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=20060502093621.GA4301@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=francis_moreau2000@yahoo.fr \
--cc=linux-mips@linux-mips.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