linux-kernel - Re: [RFC, PATCH 0/5] Going forward with Resource Management

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: <44D39BEE.9080304@watson.ibm.com>
Date:	Fri, 04 Aug 2006 15:11:42 -0400
From:	Shailabh Nagar <nagar@...son.ibm.com>
To:	rohitseth@...gle.com
CC:	Kirill Korotaev <dev@...ru>, vatsa@...ibm.com,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Andrew Morton <akpm@...l.org>, mingo@...e.hu,
	nickpiggin@...oo.com.au, sam@...ain.net,
	linux-kernel@...r.kernel.org, dev@...nvz.org, efault@....de,
	balbir@...ibm.com, sekharan@...ibm.com, haveblue@...ibm.com,
	pj@....com
Subject: Re: [RFC, PATCH 0/5] Going forward with Resource Management - A	cpu
 controller

Rohit Seth wrote:

>>>The use cases I have heard of which would benefit such a feature is
>>>(say) for database threads which want to change their "resource
>>>affinity" status depending on which customer query they are currently handling. 
>>>If they are handling a query for a "important" customer, they will want affinied
>>>to a high bandwidth resource container and later if they start handling
>>>a less important query they will want to give up this affinity and
>>>instead move to a low-bandwidth container.
> 
> 
> hmm, would it not be better to have a thread each in two different
> containers for handling different kind of requests.  

Its possible but now you're effectively requiring the thread pool to
expand as many times as service levels supported.

any long running job whose prioritization changes during its lifetime
also benefits from being able to be moved.


> Or if there is too
> much of sharing between threads, then setting the individual priority
> should help.
> 
-
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/