On Thu, May 22, 2014 at 2:18 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 21.05.14 14:02, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
Hi Cho,
Do you have any technical reason why CPU shares are reverted back to
the default value on StartupFinished but instead when the
On Thu, 22.05.14 08:42, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
On Thu, May 22, 2014 at 2:18 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 21.05.14 14:02, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
Hi Cho,
Do you have any technical reason why CPU
On Thu, May 22, 2014 at 9:07 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Thu, 22.05.14 08:42, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
On Thu, May 22, 2014 at 2:18 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 21.05.14 14:02, Umut Tezduyar Lindskog
On 05/22/2014 05:01 PM, Umut Tezduyar Lindskog wrote:
On Thu, May 22, 2014 at 9:07 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Thu, 22.05.14 08:42, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
On Thu, May 22, 2014 at 2:18 AM, Lennart Poettering
lenn...@poettering.net wrote:
Hi Cho,
Do you have any technical reason why CPU shares are reverted back to
the default value on StartupFinished but instead when the unit is in
activated state?
Through out the boot, until StartupFinished, a unit might get
activated quite early but still having a higher CPU share. If the
On 05/21/2014 09:02 PM, Umut Tezduyar Lindskog wrote:
Hi Cho,
Do you have any technical reason why CPU shares are reverted back to
the default value on StartupFinished but instead when the unit is in
activated state?
Sorry, I couldn't understand what you say. Did you mean if service has
On Wed, May 21, 2014 at 3:54 PM, WaLyong Cho walyong@samsung.com wrote:
On 05/21/2014 09:02 PM, Umut Tezduyar Lindskog wrote:
Hi Cho,
Do you have any technical reason why CPU shares are reverted back to
the default value on StartupFinished but instead when the unit is in
activated state?
On Fri, 16.05.14 00:09, WaLyong Cho (walyong@samsung.com) wrote:
Heya,
Similar to CPUShares= and BlockIOWeight= respectively. However only
assign the specified weight during startup. Each control group
attribute is re-assigned as weight by CPUShares=weight and
BlockIOWeight=weight after
On Wed, 21.05.14 14:02, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
Hi Cho,
Do you have any technical reason why CPU shares are reverted back to
the default value on StartupFinished but instead when the unit is in
activated state?
Well, the startup is only considered finished when
Similar to CPUShares= and BlockIOWeight= respectively. However only
assign the specified weight during startup. Each control group
attribute is re-assigned as weight by CPUShares=weight and
BlockIOWeight=weight after startup. If not CPUShares= or
BlockIOWeight= be specified, then the attribute is
On 05/16/2014 12:09 AM, WaLyong Cho wrote:
Similar to CPUShares= and BlockIOWeight= respectively. However only
assign the specified weight during startup. Each control group
attribute is re-assigned as weight by CPUShares=weight and
BlockIOWeight=weight after startup. If not CPUShares= or
On 04/24/2014 06:15 AM, Lennart Poettering wrote:
On Wed, 26.03.14 00:12, WaLyong Cho (walyong@samsung.com) wrote:
On 03/25/2014 05:01 AM, Lennart Poettering wrote:
On Tue, 25.03.14 01:03, WaLyong Cho (walyong@samsung.com) wrote:
/* Figure out which controllers we need */
On Wed, 26.03.14 00:12, WaLyong Cho (walyong@samsung.com) wrote:
On 03/25/2014 05:01 AM, Lennart Poettering wrote:
On Tue, 25.03.14 01:03, WaLyong Cho (walyong@samsung.com) wrote:
/* Figure out which controllers we need */
-if (c-cpu_accounting ||
On 03/26/2014 12:12 AM, WaLyong Cho wrote:
On 03/25/2014 05:01 AM, Lennart Poettering wrote:
On Tue, 25.03.14 01:03, WaLyong Cho (walyong@samsung.com) wrote:
/* Figure out which controllers we need */
-if (c-cpu_accounting || c-cpu_shares != 1024)
+if
On 03/25/2014 05:01 AM, Lennart Poettering wrote:
On Tue, 25.03.14 01:03, WaLyong Cho (walyong@samsung.com) wrote:
/* Figure out which controllers we need */
-if (c-cpu_accounting || c-cpu_shares != 1024)
+if (c-cpu_accounting ||
+
Similar to CPUShares= and BlockIOWeight= respectively. However only
assign the specified weight during startup. Each control group
attribute is re-assigned as weight by CPUShares=weight and
BlockIOWeight=weight after startup. If not CPUShares= or
BlockIOWeight= be specified, then the attribute is
On Tue, 25.03.14 01:03, WaLyong Cho (walyong@samsung.com) wrote:
/* Figure out which controllers we need */
-if (c-cpu_accounting || c-cpu_shares != 1024)
+if (c-cpu_accounting ||
+c-startup_cpu_shares != 1024 ||
+(manager_state(m) !=
Similar to CPUShares= and BlockIOWeight= respectively. However only
assign the specified weight during startup state. Each control group
attribute is re-assigned as weight by CPUShares=weight and
BlockIOWeight=weight after startup. If not CPUShares= or
BlockIOWeight= be specified, then the
On Wed, 05.03.14 17:41, WaLyong Cho (walyong@samsung.com) wrote:
Similar to CPUShares= and BlockIOWeight= respectively. However only
assign the specified weight during startup. Each control group
attribute is re-assigned as weight by CPUShares=weight and
BlockIOWeight=weight after
On 03/06/2014 03:40 AM, David Timothy Strauss wrote:
When is startup considered over? I'd like if it meant before the
WantedBy unit was started so this value still has use for arbitrary
startup.
Lennard suggested this idea.
Similar to CPUShares= and BlockIOWeight= respectively. However only
assign the specified weight during startup. Each control group
attribute is re-assigned as weight by CPUShares=weight and
BlockIOWeight=weight after startup. If not CPUShares= or
BlockIOWeight= be specified, then the attribute is
When is startup considered over? I'd like if it meant before the
WantedBy unit was started so this value still has use for arbitrary
startup.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
22 matches
Mail list logo
