From: Venkat Subbiah <vsubbiah@caviumnetworks.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "Subbiah, Venkat" <Venkat.Subbiah@caviumnetworks.com>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: task switch from net-rx to idle when there is napi processing to be done
Date: Wed, 25 Jan 2012 03:30:51 -0800 [thread overview]
Message-ID: <4F1FE7EB.3030601@caviumnetworks.com> (raw)
In-Reply-To: <20120125085523.GG6305@pengutronix.de>
On 01/25/2012 12:55 AM, Uwe Kleine-König wrote:
> Hello,
>
> On Tue, Jan 24, 2012 at 06:39:34PM -0800, Venkat Subbiah wrote:
>> In the process of debugging a napi ethernet driver performance
>> issue, what I am noticing is
>>
>> 1. While the driver is in the middle of a napi packet processing
>> loop, there is a task switch from
>> sirq-net-rx to idle even though there is pending napi processing to be done.
> I didn't check your logs below, but maybe this is related to the default
> settings in /proc/sys/kernel/sched_rt_period_us and
> /proc/sys/kernel/sched_rt_runtime_us? That is 0.05s per second is
> reserved for non-RT tasks tasks such that a run-away realtime process
> will not lock up the machine.
>
> To verify that, try
>
> echo -1> /proc/sys/kernel/sched_rt_runtime_us
>
> .
Thanks for you response. That was it. Setting this to -1 does the expected.
Then I tried playing with these settings and set
/proc/sys/kernel/sched_rt_runtime_us to 95000
/proc/sys/kernel/sched_rt_period_us to 100000
And even with the switch from sirq-net-rx to idle happens every seconds
and stays in idle for 0.05 seconds. Are they any restrictions on what
these can be set to? I guess these setting may not be reasonable. I did
verify by doing a cat of these files and read back the expected values.
Then I tried
/proc/sys/kernel/sched_rt_period_us to 1000000
/proc/sys/kernel/sched_rt_runtime_us to 980000
Even here the idle is for 0.05 seconds
> Best regards
> Uwe
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-25 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 2:39 task switch from net-rx to idle when there is napi processing to be done Venkat Subbiah
2012-01-25 8:55 ` Uwe Kleine-König
2012-01-25 9:18 ` Mike Galbraith
2012-01-25 11:40 ` Venkat Subbiah
2012-01-25 11:30 ` Venkat Subbiah [this message]
2012-01-26 15:29 ` Steven Rostedt
2012-01-26 20:35 ` Venkat Subbiah
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=4F1FE7EB.3030601@caviumnetworks.com \
--to=vsubbiah@caviumnetworks.com \
--cc=Venkat.Subbiah@caviumnetworks.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.