| Message ID | 1507883117-24347-1-git-send-email-antonio.fischetti@intel.com |
|---|---|
| Headers | show |
| Series | Conntrack: add commands to r/w CT parameters. | expand |
On Fri, Oct 13, 2017 at 09:25:12AM +0100, antonio.fischetti@intel.com wrote: > This change comes from the consideration that when the CT is enabled > the overall performance can be deeply affected, even with simple > firewall rules and with stateless protocols like UDP. > This implementation adds a basic infrastructure that allows the user > to adjust the CT configuration parameters at run-time in order to > find a better tuning. > For example - depending on the traffic profile - the user could decrease > at run-time the maximum number of tracked connections, so to mitigate > the impact on performance. > > V3: Added changes to documentation. > > V2: Reworked based on comments. > Patch #1 comes after a discussion with Darrell. > > V1: First implementation. Hi Darrell. The userspace connection tracker is mostly your code. Do you want to review this series? Otherwise, let me know, and I'll do my best.
I’ll look at these in detail Ben
Thanks Darrell
On 11/3/17, 2:49 PM, "ovs-dev-bounces@openvswitch.org on behalf of Ben Pfaff" <ovs-dev-bounces@openvswitch.org on behalf of blp@ovn.org> wrote:
On Fri, Oct 13, 2017 at 09:25:12AM +0100, antonio.fischetti@intel.com wrote:
> This change comes from the consideration that when the CT is enabled
> the overall performance can be deeply affected, even with simple
> firewall rules and with stateless protocols like UDP.
> This implementation adds a basic infrastructure that allows the user
> to adjust the CT configuration parameters at run-time in order to
> find a better tuning.
> For example - depending on the traffic profile - the user could decrease
> at run-time the maximum number of tracked connections, so to mitigate
> the impact on performance.
>
> V3: Added changes to documentation.
>
> V2: Reworked based on comments.
> Patch #1 comes after a discussion with Darrell.
>
> V1: First implementation.
Hi Darrell. The userspace connection tracker is mostly your code. Do
you want to review this series? Otherwise, let me know, and I'll do my
best.
_______________________________________________
dev mailing list
dev@openvswitch.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=edCCE36XXXeIHc0gj-Q0g9UV92jeGIxFHuFOdSQGwyc&s=NMnXxlgV8pDkn-5fI4MXaq0mJfdBIAD3h6ZfCmpVR8Q&e=
This change comes from the consideration that when the CT is enabled the overall performance can be deeply affected, even with simple firewall rules and with stateless protocols like UDP. This implementation adds a basic infrastructure that allows the user to adjust the CT configuration parameters at run-time in order to find a better tuning. For example - depending on the traffic profile - the user could decrease at run-time the maximum number of tracked connections, so to mitigate the impact on performance. V3: Added changes to documentation. V2: Reworked based on comments. Patch #1 comes after a discussion with Darrell. V1: First implementation. Fischetti, Antonio (5): dpctl: Add a comment to functions retrieving the datapath name. conntrack: add commands to r/w CT parameters. conntrack: r/w upper limit connection value. conntrack: read current nr of connections. doc: ConnTracker cfg parameters. Documentation/intro/install/dpdk.rst | 25 +++++++++ lib/conntrack.c | 90 ++++++++++++++++++++++++++++++ lib/conntrack.h | 3 + lib/ct-dpif.c | 28 ++++++++++ lib/ct-dpif.h | 2 + lib/dpctl.c | 104 ++++++++++++++++++++++++++++++++++- lib/dpctl.man | 10 ++++ lib/dpif-netdev.c | 19 +++++++ lib/dpif-netlink.c | 2 + lib/dpif-provider.h | 4 ++ 10 files changed, 286 insertions(+), 1 deletion(-)