All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: lvs-users@linuxvirtualserver.org,
	Inju Song <inju.song@navercorp.com>,
	lvs-devel@vger.kernel.org, Simon Horman <horms@verge.net.au>,
	brouer@redhat.com, Quentin Armitage <quentin@armitage.org.uk>
Subject: Re: [PATCH v2 0/3] ipvsadm: Document/add support for fo/ovf/mh schedulers
Date: Tue, 22 Jan 2019 12:02:35 +0100	[thread overview]
Message-ID: <20190122120235.0a98b47d@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1901170203590.8721@ja.home.ssi.bg>


On Thu, 17 Jan 2019 02:09:22 +0200 (EET) Julian Anastasov <ja@ssi.bg> wrote:

> On Wed, 16 Jan 2019, Quentin Armitage wrote:
> 
> > The kernel supports the fo, ovf and mh IPVS schedulers, but ipvsadm has not
> > yet been updated to document/support them. Currently ipvsadm can support them,
> > but users of ipvsadm will not be aware of their existence without reading the
> > kernel sources.
> > 
> > The following patches document support for these schedulers, and also adds
> > new flags mh-fallback and mh-port.
> > 
> > Changes since v1:
> > - Correct description of fo scheduler
> > - Correct description of ovf scheduler
> > - Completely rewrite description of mh scheduler
> > - Move definitions of IP_VS_SVC_F_SCHED_MH* from ipvsadm.c to libipvs/ip_vs.h
> > - Don't print flag-3 for SH and MH schedulers
> > 
> > With many thanks to Julian Anastasov for pointing out the errors in the
> > v1 patches and the suggested improvements.
> > 
> > Quentin Armitage (3):
> >   ipvsadm: Document support of fo scheduler
> >   ipvsadm: Document support of ovf scheduler
> >   ipvsadm: Add support for mh scheduler
> > 
> >  SCHEDULERS      |  2 +-
> >  ipvsadm.8       | 18 ++++++++++++++++++
> >  ipvsadm.c       | 17 +++++++++++++++--
> >  libipvs/ip_vs.h |  3 +++
> >  4 files changed, 37 insertions(+), 3 deletions(-)  
> 
> 	The 3 patches look ok to me. Thanks!
> 
> Acked-by: Julian Anastasov <ja@ssi.bg>
> 
> 	Jesper, you can apply them if there are no other
> suggestions/comments.

Nobody else objected, thus I've applied this patchset to git tree:
  https://git.kernel.org/pub/scm/utils/kernel/ipvsadm/ipvsadm.git/

Thank you Quentin for keeping this tool up-to-date.
-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

      reply	other threads:[~2019-01-22 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 22:55 [PATCH v2 0/3] ipvsadm: Document/add support for fo/ovf/mh schedulers Quentin Armitage
2019-01-17  0:09 ` Julian Anastasov
2019-01-22 11:02   ` Jesper Dangaard Brouer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190122120235.0a98b47d@redhat.com \
    --to=brouer@redhat.com \
    --cc=horms@verge.net.au \
    --cc=inju.song@navercorp.com \
    --cc=ja@ssi.bg \
    --cc=lvs-devel@vger.kernel.org \
    --cc=lvs-users@linuxvirtualserver.org \
    --cc=quentin@armitage.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.