All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Julian Anastasov <ja@ssi.bg>
Cc: Simon Horman <horms@verge.net.au>,
	lvs-devel@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/3] ipvs: extend connection flags to 32 bits
Date: Fri, 17 Sep 2010 14:20:48 +0200	[thread overview]
Message-ID: <4C935D20.2020901@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.58.1009162339520.6976@u.domain.uli>

Am 16.09.2010 22:42, schrieb Julian Anastasov:
> 
> 	Extend connection flags to 32 bits:
> 
> - the sync protocol supports 16 bits only, so bits 0..15 should be
> used only for flags that should go to backup server, bits 16 and
> above should be allocated for flags not sent to backup.
> 
> - use IP_VS_CONN_F_DEST_MASK as mask of connection flags in
> destination that can be changed by user space
> 
> - allow IP_VS_CONN_F_ONE_PACKET to be set in destination

Applied, thanks.

      reply	other threads:[~2010-09-17 12:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 20:42 [PATCH 1/3] ipvs: extend connection flags to 32 bits Julian Anastasov
2010-09-17 12:20 ` Patrick McHardy [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=4C935D20.2020901@trash.net \
    --to=kaber@trash.net \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=lvs-devel@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    /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.