|
On Sun, Apr 01, 2018 at 01:59:16PM +0300, Julian Anastasov wrote:
>
> Hello,
>
> On Tue, 27 Mar 2018, Inju Song wrote:
>
> > Implements the Google's Maglev hashing algorithm as a IPVS scheduler.
> > Basically it provides consistent hashing but offers some special
> > features about disruption and load balancing.
> >
> > 1) minimal disruption: when the set of destinations changes,
> > a connection will likely be sent to the same destination
> > as it was before.
> >
> > 2) load balancing: each destination will receive an almost
> > equal number of connections.
> >
> > Seel also: [3.4 Consistent Hasing] in
> > https://www.usenix.org/system/files/conference/nsdi16/nsdi16-paper-eisenbud.pdf
> >
> > v1: Add maglev consistent hasing
> >
> > v2: Add and refactor some features about MH and attach distribution test
> > results based on the MH's realtive weights.
> >
> > v3: Optimize some features, clean up strcutures of MH, rearrange
> > patchset order with new patches and so on.
> >
> > v4: Attach MH state to svc->sched_data only on success and free the
> > state when RCU callback is called.
>
> Great, v4 of the patchset looks good to me. Thanks!
>
> Signed-off-by: Julian Anastasov <ja@xxxxxx>
>
> Simon, I know it is late for the current net-next,
> so I'm not sure whether you can keep the patchset or it
> should be resubmitted later.
Thanks Inju for the patch-set and thanks Julian for the review.
I was on holiday last week and it is now certainly too late for net-next.
I have applied these patches to ipvs-next and will submit them for inclusion
in v4.18.
--
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
|
