linux-kernel - Re: [PATCH 1/1] work_on_cpu: use in drivers/pci/pci-driver.c

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]

Message-Id: <200812091452.48824.jbarnes@virtuousgeek.org>
Date:	Tue, 9 Dec 2008 14:52:48 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] work_on_cpu: use in drivers/pci/pci-driver.c

On Monday, December 01, 2008 12:20 am Rusty Russell wrote:
> This uses work_on_cpu(), rather than altering the cpumask of the
> thread which we happen to be.
>
> Note the cleanups:
>
> 1) I've removed the CONFIG_NUMA test, since dev_to_node() returns -1
>    for !CONFIG_NUMA anyway and the compiler will eliminate it.
>
> 2) No need to reset mempolicy to default (a bad idea anyway) since
>    work_on_cpu is run from a workqueue.
>
> Signed-off-by: Rusty Russell <rusty@...tcorp.com.au>
> Cc: Jesse Barnes <jbarnes@...tuousgeek.org>

Nice, I applied this to my linux-next branch to get some build/test coverage.  
Please cc linux-pci in the future though.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/