From: Rik van Riel <riel@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: fweisbec@gmail.com, tglx@linutronix.de, mingo@kernel.org,
luto@amacapital.net, peterz@infradead.org, clark@redhat.com,
eric.dumazet@gmail.com
Subject: Re: [PATCH 0/4 v5] sched,time: reduce nohz_full syscall overhead 40%
Date: Mon, 8 Feb 2016 16:07:24 -0500 [thread overview]
Message-ID: <56B9038C.5050702@redhat.com> (raw)
In-Reply-To: <1454433586-3234-1-git-send-email-riel@redhat.com>
On 02/02/2016 12:19 PM, riel@redhat.com wrote:
> (v5: address comments by Frederic & Peter, fix bug found by Eric)
>
> Running with nohz_full introduces a fair amount of overhead.
> Specifically, various things that are usually done from the
> timer interrupt are now done at syscall, irq, and guest
> entry and exit times.
It looks like nobody has objections to my v5
series.
Is there anything else I need to do before these
patches can get merged?
Also, who is going to merge these patches into
their tree?
Frederic? Thomas? Ingo?
--
All rights reversed
next prev parent reply other threads:[~2016-02-08 21:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 17:19 riel
2016-02-02 17:19 ` [PATCH 1/4] sched,time: remove non-power-of-two divides from __acct_update_integrals riel
2016-02-02 17:19 ` [PATCH 2/4] acct,time: change indentation in __acct_update_integrals riel
2016-02-02 17:19 ` [PATCH 3/4] time,acct: drop irq save & restore from __acct_update_integrals riel
2016-02-02 17:19 ` [PATCH 4/4] sched,time: only call account_{user,sys,guest,idle}_time once a jiffy riel
2016-02-09 17:11 ` Frederic Weisbecker
2016-02-09 18:13 ` Rik van Riel
2016-02-09 21:20 ` Rik van Riel
2016-02-08 21:07 ` Rik van Riel [this message]
2016-02-09 2:13 ` [PATCH 0/4 v5] sched,time: reduce nohz_full syscall overhead 40% Frederic Weisbecker
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=56B9038C.5050702@redhat.com \
--to=riel@redhat.com \
--cc=clark@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome