On 19 March 2014 20:15, Dietmar Eggemann wrote:
> On 17/03/14 11:52, Peter Zijlstra wrote:
>> On Wed, Mar 12, 2014 at 01:28:07PM +, Dietmar Eggemann wrote:
> [...]
>>> By making it robust, I guess you mean that the core scheduler has to
>>> check that the provided set-ups are sane, something
On 19 March 2014 20:15, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 17/03/14 11:52, Peter Zijlstra wrote:
On Wed, Mar 12, 2014 at 01:28:07PM +, Dietmar Eggemann wrote:
[...]
By making it robust, I guess you mean that the core scheduler has to
check that the provided set-ups are
On 17/03/14 11:52, Peter Zijlstra wrote:
> On Wed, Mar 12, 2014 at 01:28:07PM +, Dietmar Eggemann wrote:
[...]
>> By making it robust, I guess you mean that the core scheduler has to
>> check that the provided set-ups are sane, something like the following
>> code snippet in sd_init()
>>
>> if
On 17/03/14 11:52, Peter Zijlstra wrote:
On Wed, Mar 12, 2014 at 01:28:07PM +, Dietmar Eggemann wrote:
[...]
By making it robust, I guess you mean that the core scheduler has to
check that the provided set-ups are sane, something like the following
code snippet in sd_init()
if
On Wed, Mar 12, 2014 at 01:28:07PM +, Dietmar Eggemann wrote:
> On 11/03/14 13:17, Peter Zijlstra wrote:
> > On Sat, Mar 08, 2014 at 12:40:58PM +, Dietmar Eggemann wrote:
> >>>
> >>> I don't have a strong opinion about using or not a cpu argument for
> >>> setting the flags of a level (it
On Wed, Mar 12, 2014 at 01:28:07PM +, Dietmar Eggemann wrote:
On 11/03/14 13:17, Peter Zijlstra wrote:
On Sat, Mar 08, 2014 at 12:40:58PM +, Dietmar Eggemann wrote:
I don't have a strong opinion about using or not a cpu argument for
setting the flags of a level (it was part of the
On 12/03/14 13:47, Vincent Guittot wrote:
> On 12 March 2014 14:28, Dietmar Eggemann wrote:
>> On 11/03/14 13:17, Peter Zijlstra wrote:
>>> On Sat, Mar 08, 2014 at 12:40:58PM +, Dietmar Eggemann wrote:
>
> I don't have a strong opinion about using or not a cpu argument for
>
On 12/03/14 13:47, Vincent Guittot wrote:
On 12 March 2014 14:28, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 11/03/14 13:17, Peter Zijlstra wrote:
On Sat, Mar 08, 2014 at 12:40:58PM +, Dietmar Eggemann wrote:
I don't have a strong opinion about using or not a cpu argument for
On 12 March 2014 14:28, Dietmar Eggemann wrote:
> On 11/03/14 13:17, Peter Zijlstra wrote:
>> On Sat, Mar 08, 2014 at 12:40:58PM +, Dietmar Eggemann wrote:
I don't have a strong opinion about using or not a cpu argument for
setting the flags of a level (it was part of the
On 11/03/14 13:17, Peter Zijlstra wrote:
> On Sat, Mar 08, 2014 at 12:40:58PM +, Dietmar Eggemann wrote:
>>>
>>> I don't have a strong opinion about using or not a cpu argument for
>>> setting the flags of a level (it was part of the initial proposal
>>> before we start to completely rework
On 11/03/14 13:17, Peter Zijlstra wrote:
On Sat, Mar 08, 2014 at 12:40:58PM +, Dietmar Eggemann wrote:
I don't have a strong opinion about using or not a cpu argument for
setting the flags of a level (it was part of the initial proposal
before we start to completely rework the build of
On 12 March 2014 14:28, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 11/03/14 13:17, Peter Zijlstra wrote:
On Sat, Mar 08, 2014 at 12:40:58PM +, Dietmar Eggemann wrote:
I don't have a strong opinion about using or not a cpu argument for
setting the flags of a level (it was part of
On Sat, Mar 08, 2014 at 12:40:58PM +, Dietmar Eggemann wrote:
> >
> >I don't have a strong opinion about using or not a cpu argument for
> >setting the flags of a level (it was part of the initial proposal
> >before we start to completely rework the build of sched_domain)
> >Nevertheless, I
On Fri, Mar 07, 2014 at 10:47:49AM +0800, Vincent Guittot wrote:
> Peter,
>
> Was the use of the cpu as a parameter in the initialization of
> sched_domain's flag a reason for asking for reworking the
> initialization of sched_domain ?
/me tries very hard to remember.. and fails.
Reading back
On Fri, Mar 07, 2014 at 10:47:49AM +0800, Vincent Guittot wrote:
Peter,
Was the use of the cpu as a parameter in the initialization of
sched_domain's flag a reason for asking for reworking the
initialization of sched_domain ?
/me tries very hard to remember.. and fails.
Reading back the
On Sat, Mar 08, 2014 at 12:40:58PM +, Dietmar Eggemann wrote:
I don't have a strong opinion about using or not a cpu argument for
setting the flags of a level (it was part of the initial proposal
before we start to completely rework the build of sched_domain)
Nevertheless, I see one
On 8 March 2014 13:40, Dietmar Eggemann wrote:
> On 07/03/14 02:47, Vincent Guittot wrote:
>>
>> On 6 March 2014 20:31, Dietmar Eggemann wrote:
>>>
>>> On 06/03/14 09:04, Vincent Guittot wrote:
On 6 March 2014 07:17, Dietmar Eggemann
wrote:
>
>
> On 05/03/14
On 8 March 2014 13:40, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 07/03/14 02:47, Vincent Guittot wrote:
On 6 March 2014 20:31, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 06/03/14 09:04, Vincent Guittot wrote:
On 6 March 2014 07:17, Dietmar Eggemann
On 07/03/14 02:47, Vincent Guittot wrote:
On 6 March 2014 20:31, Dietmar Eggemann wrote:
On 06/03/14 09:04, Vincent Guittot wrote:
On 6 March 2014 07:17, Dietmar Eggemann wrote:
On 05/03/14 07:18, Vincent Guittot wrote:
This patchset was previously part of the larger tasks packing
On 07/03/14 02:47, Vincent Guittot wrote:
On 6 March 2014 20:31, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 06/03/14 09:04, Vincent Guittot wrote:
On 6 March 2014 07:17, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 05/03/14 07:18, Vincent Guittot wrote:
This patchset was
On 6 March 2014 20:31, Dietmar Eggemann wrote:
> On 06/03/14 09:04, Vincent Guittot wrote:
>>
>> On 6 March 2014 07:17, Dietmar Eggemann wrote:
>>>
>>> On 05/03/14 07:18, Vincent Guittot wrote:
This patchset was previously part of the larger tasks packing patchset
[1].
I
On 06/03/14 09:04, Vincent Guittot wrote:
On 6 March 2014 07:17, Dietmar Eggemann wrote:
On 05/03/14 07:18, Vincent Guittot wrote:
This patchset was previously part of the larger tasks packing patchset
[1].
I have splitted the latter in 3 different patchsets (at least) to make the
thing
On 6 March 2014 07:17, Dietmar Eggemann wrote:
> On 05/03/14 07:18, Vincent Guittot wrote:
>>
>> This patchset was previously part of the larger tasks packing patchset
>> [1].
>> I have splitted the latter in 3 different patchsets (at least) to make the
>> thing easier.
>> -configuration of
On 6 March 2014 07:17, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 05/03/14 07:18, Vincent Guittot wrote:
This patchset was previously part of the larger tasks packing patchset
[1].
I have splitted the latter in 3 different patchsets (at least) to make the
thing easier.
On 06/03/14 09:04, Vincent Guittot wrote:
On 6 March 2014 07:17, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 05/03/14 07:18, Vincent Guittot wrote:
This patchset was previously part of the larger tasks packing patchset
[1].
I have splitted the latter in 3 different patchsets (at
On 6 March 2014 20:31, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 06/03/14 09:04, Vincent Guittot wrote:
On 6 March 2014 07:17, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 05/03/14 07:18, Vincent Guittot wrote:
This patchset was previously part of the larger tasks packing
On 05/03/14 07:18, Vincent Guittot wrote:
This patchset was previously part of the larger tasks packing patchset [1].
I have splitted the latter in 3 different patchsets (at least) to make the
thing easier.
-configuration of sched_domain topology (this patchset)
-update and consolidation of
On 05/03/14 07:18, Vincent Guittot wrote:
This patchset was previously part of the larger tasks packing patchset [1].
I have splitted the latter in 3 different patchsets (at least) to make the
thing easier.
-configuration of sched_domain topology (this patchset)
-update and consolidation of
This patchset was previously part of the larger tasks packing patchset [1].
I have splitted the latter in 3 different patchsets (at least) to make the
thing easier.
-configuration of sched_domain topology (this patchset)
-update and consolidation of cpu_power
-tasks packing algorithm
Based on
This patchset was previously part of the larger tasks packing patchset [1].
I have splitted the latter in 3 different patchsets (at least) to make the
thing easier.
-configuration of sched_domain topology (this patchset)
-update and consolidation of cpu_power
-tasks packing algorithm
Based on
30 matches
Mail list logo
