feat(scheduler-allocator-runner): plan generators initialise from the scheduling core (task 1.1)
xce_alloc_plan_iter_t.init takes xce_sched_core_t* instead of xce_scheduler_t*; both built-in generators, both allocators' call sites and the contract-test stub follow. The parjob purity test now shows an identical plan sequence for a NULL and a poisoned core. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
e2266582b2
commit
86ee3491dd
6 changed files with 32 additions and 32 deletions
|
|
@ -21,7 +21,7 @@
|
|||
* is usable, not just that a struct literal type-checks.
|
||||
*
|
||||
* Both stub implementations ignore the real xce_primary_resreq_t/
|
||||
* xce_scheduler_t/plan/workers arguments (ok, per the header's own
|
||||
* xce_sched_core_t/plan/workers arguments (ok, per the header's own
|
||||
* "each concrete plan-iterator implementation carries whatever it needs"
|
||||
* note) and always yield exactly one candidate before signaling stable
|
||||
* exhaustion.
|
||||
|
|
@ -45,15 +45,15 @@ typedef struct {
|
|||
|
||||
static int stub_plan_iter_init(xce_alloc_plan_iter_t* iter,
|
||||
xce_primary_resreq_t* resreq,
|
||||
xce_scheduler_t* sched)
|
||||
xce_sched_core_t* core)
|
||||
{
|
||||
stub_plan_priv_t* priv;
|
||||
|
||||
/* Stub: ignores the real resreq/sched state -- a real implementation
|
||||
/* Stub: ignores the real resreq/core state -- a real implementation
|
||||
* (parjob's combinatorial one, seqjob's trivial one) would derive its
|
||||
* plan space from resreq->maxTasks here. */
|
||||
(void)resreq;
|
||||
(void)sched;
|
||||
(void)core;
|
||||
|
||||
if (iter == NULL) {
|
||||
return -EINVAL;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue