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-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikuunLAsrtS2GhSkICkYfN_0H0jdZyo7fxjQl9b@mail.gmail.com>
Date:	Thu, 17 Jun 2010 19:02:49 +0200
From:	sebastiano spicuglia <spicuglia.sebastiano@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	a.p.zijlstra@...llo.nl, linux-kernel@...r.kernel.org
Subject: Re: Sched_class documentation

Hi Ingo,

I made many progress. But I have two doubts yet.
First: what does hrtick_start do?
I think that: if I call hrtick_start(rq, 500)  then, after 500ns, the
task_tick function will be invocated.
Is it right?
Second: if my schedule_class decides to preempt the current task, it
has to call resched_task(rq->curr).
Is it right?

Thanks in advance.
Kind Regards.
Sebastiano.

On Tue, May 25, 2010 at 9:11 AM, Ingo Molnar <mingo@...e.hu> wrote:
>
> Hi,
>
> * sebastiano.spicuglia@...l.polimi.it <sebastiano.spicuglia@...l.polimi.it> wrote:
>
>> Hi Ingo,
>>
>> excuse me for contacting you in this way.
>> I don't want hurt you.
>> I am implementing a new schedule class for my bachelor
>> project degree at Politecnico di Milano.
>> I experienced many problems but sometimes the kernel starts.
>> The main problem is the documentation.
>> Could you explain me when sched.c calls sched_class functions (
>> enqueue_task, dequeue_task, etc... )
>> and what sched_class functions should do?
>> My reverse engineering skills don't work very well and
>> in internet there are not many information about this and
>> however they are generic and incomplete.
>>
>> I am working with version 2.6.34.
>
> There's a couple of files in Documentation/sched/ which give a high-level
> description - but some of that info is outdated. Most of the documentation is
> the code itself, as usual ;-)
>
> If you have any questions, please also Cc: lkml and Peter Zijstra
> (co-maintainer of the scheduler):
>
>  Peter Zijlstra <a.p.zijlstra@...llo.nl>
>
> Thanks,
>
>        Ingo
>
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ