|
Hi Ratz,
On Tue, 1 Jul 2003, Roberto Nibali wrote:
>
> I see the cw, mw, di relation now and the added complexity. The
> update_service() callback is called for every destination addition from
> user space which in case of the wrr scheduler will update the max
> weight, correct? Quite intelligent :)
>
Yes, it is good to restart the wrr algorithm for every destination
changes (addition/deletion/weight change).
> Why do we keep the struct iphdr *iph as second parameter in
> ip_vs_{w}rr_schedule()?
>
The struct iphdr *iph is not used in the wrr. But, struct iphdr *iph is
used in the schedulers dh/sh/lblc/lblcr, so that we have to keep the
function type unified.
Cheers,
Wensong
|
