linux-kernel - Re: [PATCH] nohz1: Documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Mar 2013 15:16:42 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Christoph Lameter <cl@...ux.com>
Cc:	paulmck@...ux.vnet.ibm.com,
	Frederic Weisbecker <fweisbec@...il.com>,
	Rob Landley <rob@...dley.net>, linux-kernel@...r.kernel.org,
	josh@...htriplett.org, zhong@...ux.vnet.ibm.com,
	khilman@...aro.org, geoff@...radead.org, tglx@...utronix.de
Subject: Re: [PATCH] nohz1: Documentation

On Thu, 2013-03-21 at 18:53 +0000, Christoph Lameter wrote:
> On Thu, 21 Mar 2013, Steven Rostedt wrote:
> 
> > For now, no, if more than one process is scheduled on the CPU, we fall
> > out of dynamic tick mode. In the future, we can add SCHED_FIFO task
> > scheduled in to trigger it. But lets conquer that after we successfully
> > conquer the current changes.
> 
> Be glad to see whatever is possible merged as soon as possible. But be
> aware that we will fall out of dyntick mode at mininum every 2 seconds
> because that is when the per cpu vm stats and the slab scanning is
> occurring. These are both deferrable activities.
> 

Thanks for giving us the heads up.

Yeah, I understand your concern. Even when the current patch set is in,
I'm not claiming success. Just like how most of -rt is now in mainline.
It's not completely finished until the rest of -rt is there. I feel the
same with the dynamic tick patches. It will get in in stages. But it
truly isn't there until we have it  fully functional, that even you will
be pleased with the result ;-)

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/