linux-kernel - Re: [PATCH v3 1/4] Documentation/scheduler/sched-deadline.txt: fix terminology and improve clarity

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]

Message-ID: <5406D0D5.8030001@unitn.it>
Date:	Wed, 03 Sep 2014 10:27:01 +0200
From:	Luca Abeni <luca.abeni@...tn.it>
To:	Henrik Austad <henrik@...tad.us>
CC:	Juri Lelli <juri.lelli@....com>,
	Peter Zijlstra <peterz@...radead.org>,
	rdunlap <rdunlap@...radead.org>, Ingo Molnar <mingo@...hat.com>,
	Dario Faggioli <raistlin@...ux.it>,
	Juri Lelli <juri.lelli@...il.com>,
	LKML doc <linux-doc@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/4] Documentation/scheduler/sched-deadline.txt: fix
 terminology and improve clarity

On 09/03/2014 09:45 AM, Henrik Austad wrote:
[...]
>>      Summing up, the CBS[2,3] algorithms assigns scheduling deadlines to
>>>> tasks so
>>>>     that each task runs for at most its runtime every period, avoiding any
>>>>     interference between different tasks (bandwidth isolation), while the
>>>> EDF[1]
>>>> - algorithm selects the task with the smallest scheduling deadline as
>>>> the one
>>>> + algorithm selects the task with the closest scheduling deadline as the
>>>> one
>>>>     to be executed first.  Thanks to this feature, also tasks that do not
>>>>
>>>
>>> s/first/next/
>>>
>>> Also, next sentence does not make much sense, I would drop the also;
>>>
>>> "Thanks to this feature, tasks that do not strictly comply with the ..."
>>>
>> I agree with these changes, but they are in text that is not changed by my
>> patch, right?
>> What should I do? Add these changes to the patch, or send an additional
>> incremental
>> patch with these changes?
>>
>
> Patch is about clarity, right? I'd just add it to this patch.
Ok; I'll send an updated patch to Juri.



			Thanks,
				Luca

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