From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Subject: Re: [PATCH, RFC] mlx4: Avoid that mlx4_cmd_wait() contributes to the system load
Date: Wed, 24 Jul 2013 18:17:44 +0300 [thread overview]
Message-ID: <51EFF018.7050409@mellanox.com> (raw)
In-Reply-To: <51ED4E60.30203-HInyCGIudOg@public.gmane.org>
On 22/07/2013 18:23, Bart Van Assche wrote:
> Avoid that kernel threads running mlx4_cmd_wait() contribute to the
> system load by setting the task state to TASK_INTERRUPTIBLE instead
> of TASK_UNINTERRUPTIBLE while waiting. This patch reduces the load
> average from about 0.5 to about 0.0 on an idle system with one mlx4
> HCA and no IB cables connected.
Before diving to the implications of the patch, lets discuss the
phenomena you see...
So the load average on this idle system is 0.5 or 0.05?
I don't see 0.5 or a like on my systems that are installed with HCAs and
are idle. Could it
be that some IB management entity is repeatedly sending MADs to this
system?
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-07-24 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 15:23 [PATCH, RFC] mlx4: Avoid that mlx4_cmd_wait() contributes to the system load Bart Van Assche
[not found] ` <51ED4E60.30203-HInyCGIudOg@public.gmane.org>
2013-07-24 15:17 ` Or Gerlitz [this message]
[not found] ` <51EFF018.7050409-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-07-24 16:48 ` Bart Van Assche
[not found] ` <51F0055F.7000703-HInyCGIudOg@public.gmane.org>
2013-07-24 17:06 ` Or Gerlitz
[not found] ` <51F0097C.4010806-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-07-24 17:13 ` Bart Van Assche
2013-07-24 18:34 ` Bart Van Assche
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=51EFF018.7050409@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=bvanassche-HInyCGIudOg@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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