priority == preemptible doesn't preempt about simmer HOT 4 CLOSED

Ok, I see what's the problem: the problem is in the documentation. 😄

Suppose two arrivals with priority=preemptible=x. If preemption occurs when priority >= preemptible, then each one is able to preempt the other, and the simulator enters an infinite loop.

So I'll change the documentation to reflect that priority must be >preemptible and I'll force that, for an arrival, its preemptible parameter must be >= its priority.

from simmer.

New ?seize:

preemptible: if the seize occurs in a preemptive resource, this parameter establishes the minimum incoming priority that can preempt this arrival (a seize with a priority greater than 'preemptible' gains the resource). In any case, 'preemptible' must be equal or greater than 'priority', and thus only higher priority seizes can trigger the preemption.

from simmer.

Oh right, I see. I was confused about how FIFO/LIFO was applied, and thought it was a way of implementing a FIFO/LIFO queue. But it's purely about which arrival that is already being served will be preempted.

from simmer.

Yeap, that's right. Because, if there are several arrivals being served, all of them with the same priority, and another one comes and triggers preemption, you need a policy to select which one should be stopped. That's the meaning of FIFO/LIFO in this context.

In any case, there was this mistake in the documentation. Thanks for the report. Keen eye! 😉

BTW, eager to read the second part of your post!

from simmer.