All of lore.kernel.org
 help / color / mirror / Atom feed
From: Murat Sezgin <msezgin@codeaurora.org>
To: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: "notification events for routing changes" patch
Date: Mon, 16 Nov 2015 20:26:14 -0800	[thread overview]
Message-ID: <D26FEC66.2884B%msezgin@codeaurora.org> (raw)


Hi Jozsef,

While I was looking for a solution in the kernel for general routing
change notification implementation, I came across your following patch.

http://www.spinics.net/lists/netfilter-devel/msg24239.html


In this email chain, you said that you found another simple solution and
implemented it in the masquerade module. I saw that commit in the upstream
kernel.

But I think the patch you proposed before also very useful for the fast
path implementations. Because when a connection starts to flow through the
fast path, linux networking stack no longer sees those packets. Then, if
the route table is changed in some way, let¹s say user add/delete a route
with the ³route² or ³ip route² command, the fast path traffic will not
aware of this change. So, if we have a notification mechanism like you
have implemented, the fast path manager module can register itself to
these events and manage its connections accordingly.

Do you have any plan to push and merge this path to the upstream kernel?

Regards,
Murat


--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2015-11-17  4:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17  4:26 Murat Sezgin [this message]
2015-11-17  8:28 ` "notification events for routing changes" patch Jozsef Kadlecsik
2015-11-17 17:55   ` Murat Sezgin
2015-11-17 20:25     ` Jozsef Kadlecsik

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=D26FEC66.2884B%msezgin@codeaurora.org \
    --to=msezgin@codeaurora.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.