linux-kernel - Re: [dm-devel] Questions about the function, queue

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>] [day] [month] [year] [list]

Date:	Mon, 5 Jan 2015 09:17:08 +0000
From:	Joe Thornber <thornber@...hat.com>
To:	device-mapper development <dm-devel@...hat.com>
Cc:	agk@...hat.com, linux-raid@...r.kernel.org,
	linux-kernel@...r.kernel.org, snitzer@...hat.com
Subject: Re: [dm-devel] Questions about the function, queue_empty in
 dm-cache-policy-mq.c

On Sun, Jan 04, 2015 at 10:24:16PM -0500, nick wrote:
> Greetings All,
> I have a few questions about the function I stated in the message for this email.
> 1. What is the issues with the CPU usage for this function?

At the moment it can perform up to NR_QUEUE_LEVELS (16) list_empty()
calls.  Which I consider too much work for a function that is called
frequently.

> 2. What hardware is this on ?

Irrelevant.

> 3. How scalable is this function in terms of NR_QUEUE_LEVELS and how many does it need to handle?

Linear.  NR_QUEUE_LEVELS is a compile time constant currently set to
16, and unlikely to change.

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