From: Karim Yaghmour <karim@opersys.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Average instruction length in x86-built kernel?
Date: Fri, 29 Jul 2005 17:32:15 -0400 [thread overview]
Message-ID: <42EAA05F.4000704@opersys.com> (raw)
I'm wondering if anyone's ever done an analysis on the average length
of instructions in an x86-built kernel.
Googling around, I can find references claiming that the average
instruction length on x86 is anywhere from 2.7 to 3.5 bytes, but I
can't find anything studying Linux specifically.
Just curious,
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
next reply other threads:[~2005-07-29 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 21:32 Karim Yaghmour [this message]
2005-07-30 13:49 ` Average instruction length in x86-built kernel? Ingo Oeser
2005-07-30 19:57 ` Karim Yaghmour
2005-08-01 7:35 ` David Weinehall
[not found] <4vKU4-3sU-21@gated-at.bofh.it>
[not found] ` <4w02Q-7e6-21@gated-at.bofh.it>
[not found] ` <4w5OQ-6Z9-25@gated-at.bofh.it>
2005-07-31 2:19 ` Bodo Eggert
2005-08-01 6:25 ` Jan Engelhardt
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=42EAA05F.4000704@opersys.com \
--to=karim@opersys.com \
--cc=linux-kernel@vger.kernel.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