linux-kernel - Re: [PATCH 1/4] async: introduce 'async

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: <4FBF89C3.3050308@linux.intel.com>
Date:	Fri, 25 May 2012 06:31:47 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
CC:	Dan Williams <dan.j.williams@...el.com>, mroos@...ux.ee,
	linux-scsi@...r.kernel.org,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	linux-kernel@...r.kernel.org, Liam Girdwood <lrg@...com>
Subject: Re: [PATCH 1/4] async: introduce 'async_domain' type

On 5/25/2012 12:51 AM, James Bottomley wrote:
> On Fri, 2012-05-25 at 00:50 -0700, Dan Williams wrote:
>> This is in preparation for teaching async_synchronize_full() to sync all
>> pending async work, and not just on the async_running domain.  This
>> conversion is functionally equivalent, just embedding the existing list
>> in a new async_domain type.
> 
> This looks good, but I want Arjan and others who invented the async code
> to speed up boot to comment on all of this.  What was the intention of
> async_synchronize_full() and if it wasn't to synchronise all domains,
> should we fix the documentation and add a new primitive to do that,
> since boot clearly assumes the all domains behaviour.

it was not what was intended originally (the domains were supposed to be
completely independent beasts), however I can see that this is confusing
and even undesired, so I am ok with the change.
Ideally we get a way to have an async domain opt out of the global sync,
but until I get an actual user of that into mainline, don't worry about it.
--
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/