kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Verifying module
Date: Tue, 4 Jan 2011 12:03:12 +0700	[thread overview]
Message-ID: <AANLkTikPzvqdBf9u9M=F07i3WOoZKX94ufar6vMryJe8@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikJ2eunC1xqD+anwzD43ubpO3eRf-=0EOmU7bYa@mail.gmail.com>

Hi..

On Tue, Jan 4, 2011 at 10:15, Mag Gam <magawake@gmail.com> wrote:
> I am talking about scheduling latency and more important ?network latency

Please don't do top posting....

About measuring latency, I think you can use lmbench along with ftrace
(check http://lxr.linux.no/linux+*/Documentation/trace/events.txt for
the details). Uhm and I think you could probably use the new "perf"
tool, which is bundled in vanilla kernel tarball.

Network latency? Perhaps you can check this article "Benchmarking
network  performance with Network Pipemeter, LMbench, and nuttcp"
(http://www.linux.com/archive/feature/144532)

All in all, the things that might affect the latency stuffs IMHO are:
all tracing related functionality, traffic filtering/shaping, security
modules. even if they were indeed loaded, I think the overhead might
be negligible if you use them carefully and properly.

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

      reply	other threads:[~2011-01-04  5:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 13:06 Verifying module Mag Gam
2011-01-03 20:06 ` Mulyadi Santosa
2011-01-04  3:15   ` Mag Gam
2011-01-04  5:03     ` Mulyadi Santosa [this message]

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='AANLkTikPzvqdBf9u9M=F07i3WOoZKX94ufar6vMryJe8@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).