From: snmp snmp <snmp.ml@gmail.com>
To: linux-numa@vger.kernel.org
Subject: Query
Date: Wed, 16 Mar 2011 15:06:35 +0530 [thread overview]
Message-ID: <AANLkTi=-4cLY1oHDavCMNzcK2uCTaZ3t58XTYeBHyTvU@mail.gmail.com> (raw)
Hi ,
Me and my friends are working on a new concept.
Idea is to run different kernels on different cores in a
multicore architecture. Each kernel is performing logically different
tasks. We believe to improve the cache performance and reduce cpu idle
time. This concept can be applied to filers , graphics processing
systems , embedded systems.
Our implementation is on Intel core 2 duo machine. So far our
implementation includes running two kernels simultaneously (one on
each core) , handling hard-disk on one core and ethernet on another
core so as to divide the network and disk subsystem.
But here we are unable to measure the performance. Can u please
suggest any method to measure the performance in terms of throughput
and response time?
Thank you.
next reply other threads:[~2011-03-16 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 9:36 snmp snmp [this message]
[not found] ` <AANLkTik+c0DvFzkoAzWDXsBSkq4HyHBtA0tuxkLnKu6F@mail.gmail.com>
2011-03-17 9:13 ` Query snmp snmp
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='AANLkTi=-4cLY1oHDavCMNzcK2uCTaZ3t58XTYeBHyTvU@mail.gmail.com' \
--to=snmp.ml@gmail.com \
--cc=linux-numa@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;
as well as URLs for NNTP newsgroup(s).