From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Module vs Kernel main performacne
Date: Wed, 30 May 2012 23:45:54 +0700 [thread overview]
Message-ID: <CAGdaadazeyRAgfSxFTXCbTB5Jv_1RTtz=7gzADvxKUih3ueiMQ@mail.gmail.com> (raw)
In-Reply-To: <CACYKDtgbDPJdYHXNw=yF==-w5BNaQGBiZ_y+jKU4N9BYWxS7LA@mail.gmail.com>
Hi...
On Wed, May 30, 2012 at 11:51 AM, Abu Rasheda <rcpilot2010@gmail.com> wrote:
> When you say, LKM area is prepared with vmalloc is it for code /
> executable you refering too ?
Yes, AFAIK memory area code and static data in linux kernel module is
allocated via vmalloc().
>if so will it matter for data copy ?
see my previous reply :)
>
> Point # 2. Some one was saying that on atleast MIPS it takes more
> cycle to call kernel main function from module because of log jump.
> Does it apply to x86_64 to ?
IIRC long jump means jumping more than 64 KB...but that's in real mode
in 32 bit...so I am not sure whether it still applies in protected
mode.
> To teat above two should I make my module part of static kernel ?
good idea....i think you can try that... :)
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2012-05-30 16:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 23:50 Module vs Kernel main performacne Abu Rasheda
2012-05-30 4:18 ` Mulyadi Santosa
2012-05-30 4:51 ` Abu Rasheda
2012-05-30 16:45 ` Mulyadi Santosa [this message]
2012-05-30 21:44 ` Abu Rasheda
2012-05-31 0:17 ` Abu Rasheda
2012-05-31 5:35 ` Mulyadi Santosa
2012-05-31 13:35 ` Abu Rasheda
2012-06-01 0:27 ` Chetan Nanda
2012-06-01 18:52 ` Abu Rasheda
2012-06-07 13:11 ` Peter Senna Tschudin
2012-06-07 17:47 ` Abu Rasheda
2012-06-07 18:10 ` Peter Senna Tschudin
2012-06-09 1:52 ` Abu Rasheda
2012-06-07 23:36 ` Peter Senna Tschudin
2012-06-07 23:41 ` Abu Rasheda
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='CAGdaadazeyRAgfSxFTXCbTB5Jv_1RTtz=7gzADvxKUih3ueiMQ@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).