linux-kernel - Re: [PATCH 22/25] Generic dynamic per cpu refcounting

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: <20121129205447.GY16230@one.firstfloor.org>
Date:	Thu, 29 Nov 2012 21:54:47 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Kent Overstreet <koverstreet@...gle.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Benjamin LaHaise <bcrl@...ck.org>,
	linux-kernel@...r.kernel.org, linux-aio@...ck.org,
	linux-fsdevel@...r.kernel.org, zab@...hat.com, jmoyer@...hat.com,
	axboe@...nel.dk, viro@...iv.linux.org.uk
Subject: Re: [PATCH 22/25] Generic dynamic per cpu refcounting

> > The regular atomic_t is limited in ways that you are not.
> > See my original mail.
> 
> I don't follow, can you explain?

For most cases the reference count is tied to some object, which are
naturally limited by memory size or other physical resources.

But in the assymetric CPU case with your ref count no such limiter
exists.


-Andi
-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/