linux-kernel - Re: [PATCHSET] workqueue: remove gcwq and make worker

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: <20130124185103.GP2373@mtj.dyndns.org>
Date:	Thu, 24 Jan 2013 10:51:03 -0800
From:	Tejun Heo <tj@...nel.org>
To:	Lai Jiangshan <eag0628@...il.com>
Cc:	linux-kernel@...r.kernel.org, Lai Jiangshan <laijs@...fujitsu.com>
Subject: Re: [PATCHSET] workqueue: remove gcwq and make worker_pool the only
 backend abstraction

Hey, Lai.

On Thu, Jan 24, 2013 at 09:36:39PM +0800, Lai Jiangshan wrote:
> For the whole patchset
> Reviewed-by: Lai Jiangshan <laijs@...fujitsu.com>

Thanks for reviewing it.

> The only concern: get_work_pool() may slow down __queue_work().

Yeap, I'm currently working on to optimize idr so that the fast path
basically comes down to

	if (id < FIRST_LAYER_LIMIT)
		return idr->first_layer[id];

> I think we can save the pool->id at work_struct->entry.next, It will
> simply the code a little.

Hmm... I'm not sure whether saving id somewhere else would make any
noticeable difference.  Decoding ->id probalby comes down to a couple
bit shuffling instructions.

> More aggressive, we can save the work_pool
> pointer at work_struct->entry.next, it will simply more code and
> __queue_work() will not be slowed down. (It is the user's
> responsibility not to modify work_struct if the user want to pass it
> to workqueue API later)

We probably can't store pointers to pools directly because custom
pools will need to be dynamically created and destroyed.

Thanks.

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