lvs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: "longguang.yue" <bigclouds@163.com>
Cc: horms@verge.net.au, kadlec@netfilter.org, fw@strlen.de,
	pablo@netfilter.org, lvs-devel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH] ipvs: add a sysctl switch to control ipvs to bypass OUTPUT chain or not
Date: Thu, 25 Aug 2022 08:32:51 +0300 (EEST)	[thread overview]
Message-ID: <e1adaaad-49f-de31-1dff-183eee242dc@ssi.bg> (raw)
In-Reply-To: <31196e83.2cbe.182d3693f03.Coremail.bigclouds@163.com>

[-- Attachment #1: Type: text/plain, Size: 557 bytes --]


	Hello,

On Thu, 25 Aug 2022, longguang.yue wrote:

> I see. 
> I hope we could find a maintainable and decoupled way to keep ipvs high performance.
> especially for kubernetes environment, there are from dozens up to one hundred rules in OUTPUT chain.

	May be some rules can help the bunch of rules to
be applied only for first packet, not for every packet in
connection, such as:

iptables -t filter -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -t filter -A OUTPUT -m ipvs --ipvs -j ACCEPT

Regards

--
Julian Anastasov <ja@ssi.bg>

      parent reply	other threads:[~2022-08-25  5:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 10:07 [PATCH] ipvs: add a sysctl switch to control ipvs to bypass OUTPUT chain or not longguang.yue
2022-08-23 18:16 ` Julian Anastasov
     [not found]   ` <31196e83.2cbe.182d3693f03.Coremail.bigclouds@163.com>
2022-08-25  5:32     ` Julian Anastasov [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=e1adaaad-49f-de31-1dff-183eee242dc@ssi.bg \
    --to=ja@ssi.bg \
    --cc=bigclouds@163.com \
    --cc=fw@strlen.de \
    --cc=horms@verge.net.au \
    --cc=kadlec@netfilter.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvs-devel@vger.kernel.org \
    --cc=pablo@netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).