Hello,
On Tue, 9 Nov 2010, Simon Horman wrote:
- backup creates template but there is no PE => cp->pe remains NULL if
we want to keep conn entry. Option 2 is that we can ignore
the conn entry if the PE module is not loaded before this step
I think that is better to drop the entry as (at least the way PE SIP works)
its entirely likely that it could be used by the scheduler to use
the wont real server if the pe_data is missing. Or in other words,
it is no better than the entry being missing all together.
Agreed.
If later we have PE engines that behave differently, and creating
templates without pe_data makes sense, we can revisit this.
- svc is added => PE module is loaded (request_module)
- next sync message comes and we bind cp->dest => if cp->pe
is NULL we should set cp->pe to svc->pe. The problem here is
that svc can be added without PE, then this template will not
work as expected.
I'm unsure what you mean by "svc can be added without PE"
-A without --pe [engine] option in backup.
Regards
--
Julian Anastasov <ja@xxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe lvs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
