linux-kernel - RE: vmstat: use our own timer events

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0705021128340.646@schroedinger.engr.sgi.com>
Date:	Wed, 2 May 2007 11:29:08 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	Arjan van de Ven <arjan@...ux.intel.com>
Subject: RE: vmstat: use our own timer events

On Wed, 2 May 2007, Pallipadi, Venkatesh wrote:

> Can this use 'deferrable timer' along with round_jiffies. That
> will eliminate the issue of too frequent interrupt when CPU is idle.

Yes I asked Arjan about this.
> >+	struct delayed_work *vmstat_work = &per_cpu(vmstat_work, cpu);
> >+
> >+	INIT_DELAYED_WORK(vmstat_work, vmstat_update);
> 
> This change alone should help.
> 	INIT_DELAYED_WORK_DEFERRABLE(vmstat_work, vmstat_update);
> 

Hmmm.. I need to check out what this does exactly.

-
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/