public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>, schwidefsky@de.ibm.com
Subject: [PATCH 0/3] NO_IDLE_HZ support patches
Date: Thu, 15 Sep 2005 14:20:15 +0530	[thread overview]
Message-ID: <20050915085015.GA10191@in.ibm.com> (raw)

CONFIG_NO_IDLE_HZ (supported on s390 and ARM currently, but also gaining
x86 support very soon) lets timer ticks to be skipped on idle CPUs. This
has several implications on core kernel, which are addressed in
these patches sent in separate mails.


Patch 0/3	- 	This mail.
Patch 1/3	-	Fix a RCU race condition
Patch 2/3	- 	add_timer_on needs to check for wakeup of
			sleeping CPU.
Patch 3/3	- 	Take care of scheduler load imbalance because
			rebalance does not happen when idle
			CPU shuts of ticks for extended periods.
			(This is more of place holder right now for
			a real patch).
			

-- 


Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017

                 reply	other threads:[~2005-09-15  8:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050915085015.GA10191@in.ibm.com \
    --to=vatsa@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    /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