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:	Sun, 22 Oct 2006 23:15:15 -0700
From:	yhlu <yhlu.kernel@...il.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	"Andi Kleen" <ak@...e.de>, "Muli Ben-Yehuda" <muli@...ibm.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...l.org>
Subject: Re: [PATCH 1/2] x86_64 irq: Simplify the vector allocator.

On 10/22/06, Eric W. Biederman <ebiederm@...ssion.com> wrote:
>
> There is no reason to remember a per cpu position of which vector
> to try.  Keeping a global position is simpler and more likely to
> result in a global vector allocation even if I don't need or require
> it.  For level triggered interrupts this means we are less likely to
> acknowledge another cpus irq, and cause the level triggered irq to
> harmlessly refire.
>
> This simplification makes it easier to only access data structures
> of  online cpus, by having fewer special cases to deal with.
>
>
> Signed-off-by: Eric W. Biederman <ebiederm@...ssion.com>

Good, It will keep increase vector, and only try to use same vector for
different cpu when vector is used up.

Acked-by: Yinghai Lu <yinghai.lu@....com>
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ