From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Flavio Leitner <fbl@redhat.com>
Cc: netdev@vger.kernel.org, Joe Stringer <joe@ovn.org>,
Pravin B Shelar <pshelar@ovn.org>,
dev@openvswitch.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/4] openvswitch: load and reference the NAT helper
Date: Tue, 30 Apr 2019 13:42:40 +0200 [thread overview]
Message-ID: <20190430114240.bpqseexjjcr6s4ta@salvia> (raw)
In-Reply-To: <20190417144617.14922-1-fbl@redhat.com>
On Wed, Apr 17, 2019 at 11:46:13AM -0300, Flavio Leitner wrote:
> The request_module() is quite expensive and triggers the
> usermode helper in userspace. Instead, load only if the
> module is not present and keep module references to avoid
> problems.
>
> The first patch standardize the module alias which is already
> there, but not in a formal way.
>
> The second patch adds an API to point to the NAT helper.
>
> The third patch will register each NAT helper using the
> new API.
>
> The last patch fixes openvswitch to use the new API to
> load and reference the NAT helper and also report an error
> if the operation fails.
Series applied. Thanks Flavio.
prev parent reply other threads:[~2019-04-30 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 14:46 [PATCH net-next v3 0/4] openvswitch: load and reference the NAT helper Flavio Leitner
2019-04-17 14:46 ` [PATCH net-next v3 1/4] netfilter: use macros to create module aliases Flavio Leitner
2019-04-17 14:46 ` [PATCH net-next v3 2/4] netfilter: add API to manage NAT helpers Flavio Leitner
2019-04-17 14:46 ` [PATCH net-next v3 3/4] netfilter: nf_nat: register " Flavio Leitner
2019-04-17 14:46 ` [PATCH net-next v3 4/4] openvswitch: load and reference the NAT helper Flavio Leitner
2019-04-18 6:25 ` [PATCH net-next v3 0/4] " David Miller
2019-04-18 11:28 ` Pablo Neira Ayuso
2019-04-30 11:42 ` Pablo Neira Ayuso [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=20190430114240.bpqseexjjcr6s4ta@salvia \
--to=pablo@netfilter.org \
--cc=dev@openvswitch.org \
--cc=fbl@redhat.com \
--cc=joe@ovn.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pshelar@ovn.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.