Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: callum.sinclair@alliedtelesis.co.nz
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
	nikolay@cumulusnetworks.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, nicolas.dichtel@6wind.com
Subject: Re: [PATCH net-next v6] ipmr: ip6mr: Create new sockopt to clear mfc cache or vifs
Date: Thu, 21 Feb 2019 13:05:28 -0800 (PST)	[thread overview]
Message-ID: <20190221.130528.1962020421176856619.davem@davemloft.net> (raw)
In-Reply-To: <20190217210752.20914-1-callum.sinclair@alliedtelesis.co.nz>

From: Callum Sinclair <callum.sinclair@alliedtelesis.co.nz>
Date: Mon, 18 Feb 2019 10:07:51 +1300

> Created a way to clear the multicast forwarding cache on a socket
> without having to either remove the entries manually using the delete
> entry socket option or destroy and recreate the multicast socket.
> 
> Calling the socket option MRT_FLUSH will allow any combination of the
> four flag options to be cleared.
> 
> MRT_FLUSH_MFC will clear all non static mfc entries and clear the unresolved cache
> MRT_FLUSH_MFC_STATIC will clear all static mfc entries
> MRT_FLUSH_VIFS will clear all non static interfaces
> MRT_FLUSH_VIFS_STATIC will clear all static interfaces.

Applied.

      parent reply	other threads:[~2019-02-21 21:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 21:07 [PATCH net-next v6] ipmr: ip6mr: Create new sockopt to clear mfc cache or vifs Callum Sinclair
2019-02-17 21:07 ` Callum Sinclair
2019-02-18 12:31   ` Nikolay Aleksandrov
2019-02-21 21:05 ` David Miller [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=20190221.130528.1962020421176856619.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=callum.sinclair@alliedtelesis.co.nz \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=nikolay@cumulusnetworks.com \
    --cc=yoshfuji@linux-ipv6.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