linux-kernel - Re: [PATCH] Documentation/scheduler/sched-deadline.txt: correct definition of density as C_i/min{D_i,P

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]

Date:	Tue, 07 Apr 2015 11:48:07 +0200
From:	Luca Abeni <luca.abeni@...tn.it>
To:	Henrik Austad <henrik@...tad.us>
CC:	Zhiqiang Zhang <zhangzhiqiang.zhang@...wei.com>,
	juri.lelli@....com, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: [PATCH] Documentation/scheduler/sched-deadline.txt: correct definition
 of density as C_i/min{D_i,P_i}

On 04/03/2015 09:47 PM, Luca Abeni wrote:
> On Fri, 3 Apr 2015 19:57:37 +0200
> Henrik Austad <henrik@...tad.us> wrote:
[...]
>> I realise that I've reviewed quite a lot of this, and I have some
>> vague memories of this being discussed earlier, Juri? Luca?
> I remember there was a discussion (and I seem to remember that the
> symbol used for the period was changed at least one time, but I might
> be wrong), but I do not remember the details.
>
> Next week I'll have some time for working on this; I'll search the old
> emails and I'll try to reconstruct the discussion.
Sorry, after searching in my old emails I've not been able to find
references to this particular topic (T_i vs P_i).
Maybe I lost some emails, or maybe I mis-remembered the old discussion...

Anyway, as I said I am fine with changing P_i in T_i if there is a general
agreement.



				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/