From: "Mohamed Bamakhrama" <bamakhrama@gmail.com>
To: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Average number of instructions per line of kernel code
Date: Thu, 30 Aug 2007 15:00:29 +0200 [thread overview]
Message-ID: <40378e40708300600h5837d46ci5266b8ae62bbd46e@mail.gmail.com> (raw)
Hi all,
I have a question regarding the average number of assembly
instructions per line of kernel code. I know that this is a difficult
question since it depends on many factors such as the instruction set
architecture, compiler used, optimizations used, type of code, coding
style, etc...
I would like to know a rough estimate for such a quantity for the
kernel 2.4/2.6 code running on MIPS32 architecture.
My estimate is between 5-10 instructions. I googled for such a thing
but couldn't find any useful papers/resources.
Many thanks in advance.
Best regards
--
Mohamed A. Bamakhrama
next reply other threads:[~2007-08-30 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 13:00 Mohamed Bamakhrama [this message]
2007-08-30 13:31 ` Jesper Juhl
2007-08-30 13:48 ` Mohamed Bamakhrama
2007-08-30 13:54 ` Jesper Juhl
2007-08-30 16:29 ` J. Scott Kasten
2007-08-30 19:49 ` Jan Engelhardt
2007-08-30 19:56 ` Freddy Spierenburg
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=40378e40708300600h5837d46ci5266b8ae62bbd46e@mail.gmail.com \
--to=bamakhrama@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®