Re: [pok-devel] Proposing a patch to sched.c

[Jeremy Rosen <jeremy.rosen@xxxxxxxxxxx>]

I had a similar need and developed a patch of my own, but it wasn't in a commitable state yet, just for testing so far...

my approch was a bit different (the flush happened per-port at write time) but your patch would fullfill my need too...


I'm looking forward to seeing this commited...

    Cordialement

    Jérémy Rosen

fight key loggers : write some perl using vim

----- Mail original -----
> Dear POK users and contributors,
> We propose to integrate the following functionality in POK concerning
> inter-partition communications.
> The purpose is to propose alternatives to the default flushing
> policy. This proposal is the outcome of a joint
> work in our research group with Etienne Borde and Laurent Pautet.
>
> Up to now the flushing policy cannot be configured and consist in a
> periodic flush at each Major Frame beginning.
> In industry two other configurations are often considered:
> Pol1: Periodic flush with a period dividing the Major Frame.
> Pol2: Systematic flush of partition outgoing ports when leaving its
> scheduling slot.
>
> We propose the following code to handle these two additional
> semantics and handle their selection. The code is still compatible
> with ocarina (the default policy is still the one used before).
>
> Even if we do not propose to update ocarina to handle pre processor
> macro definition to activate them, we
> take advantage of this proposal to inform you that we are developing
> an Eclipse plug-in integrated with the OSATE  framework to handle
> pok code generation. If you are interested we can provide you access
> to the current state of the project.
>
> More detail on the patch :
> Files affected : sched.c
> Optional : new example directory with model integrating properties
> used in our code generation framework to activate the different
> policies.
>
> You can find attached the diff of the affected file with the latest
> revision of POK (#44).
>
> Pol1 is activated when the following macro is defined :
> POK_FLUSH_PERIOD
> You need to bind it to a value dividing Major Frame duration (should
> be checked / enforced at code generation time)
>
> Pol2 will be activated when the following macro is defined :
> POK_NEEDS_FLUSH_ON_WINDOWS
> No particular value is required
>
> If none are defined the default behavior is enforced.
> We 'd like to know your point of view about integrating these
> functionalities, as is or with limited modifications, in POK trunk.
>
> Best regards,
> Thomas ROBERT
> -------------------
> Lecturer,
> Telecom ParisTech - Département INFRES
> 46 rue Barrault, 75634 Paris Cedex 13
> France.
> -------------------
> tel : (+33) (0) 145817749
> -------------------
>
>