From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BF493C169C4 for ; Fri, 8 Feb 2019 21:40:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8EBA621908 for ; Fri, 8 Feb 2019 21:40:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=cumulusnetworks.com header.i=@cumulusnetworks.com header.b="BSp9/nVF" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727361AbfBHVkk (ORCPT ); Fri, 8 Feb 2019 16:40:40 -0500 Received: from mail-wm1-f66.google.com ([209.85.128.66]:35986 "EHLO mail-wm1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726353AbfBHVkj (ORCPT ); Fri, 8 Feb 2019 16:40:39 -0500 Received: by mail-wm1-f66.google.com with SMTP id p6so5596163wmc.1 for ; Fri, 08 Feb 2019 13:40:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cumulusnetworks.com; s=google; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=JtYsIJMBQi0vtP7DpovmthczfVtlb0mp9thjyJS3IU8=; b=BSp9/nVFDZQm/FJYXWLkjEHZA1U1CdQwjdKWyCRlt92UXgwAlpzzyMPwArrE2nW0ef GYMIQpIf0FAvnW3UOy/EwY98ViqUHwuo+hRq3kKjyvhWo497KwzliWpn9wRTeGSFC/el NxYjugSRZDUd2WINXf8H93PAvzAD68QqbtrhQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=JtYsIJMBQi0vtP7DpovmthczfVtlb0mp9thjyJS3IU8=; b=KXuVbCbUohhsW+gRnTLQSlt+YdB2/5BHJ7YWx2G3cwsRIog6aLKFyxKYuenXwr1G83 WhF11eMQOrb1BuxALKGBVA07/+Sm1VceMP7/8rKoXwfxqrVpDOknRq7wycHogSLiNvsx KPfSMjTS3Xs97x9jZDAb8eQt0Pp2cFefb4Kr23gQeYHhdugbb8E3KkTeFauGm/ax4OLh UYNZdMWgyPoOmQGEX3jcB3vGmbl/fLSFE40H8QWUmPDN3f1ttF0JQz29DC3I5n2o1V27 B1omAZFZw2sg9dNLL5X4z2aY85CGNT55KIFTva3LzHvitw4S3V4ZfDCc5kGhCB0nGbjQ 1/AA== X-Gm-Message-State: AHQUAuayEI/RQdVLNSuY0cnw0X14ar8d05cqRF4Lp3SFNw1ZvL8f4Ea0 9k3GqxXvn9FSblwNcf51Pa+FuA== X-Google-Smtp-Source: AHgI3IaIxUWHMrF/NHwOSeNQkRW2jM/xh/HeKDbQbr9D1xGsmZExM1CuLgcPRcJlVQHSru9EUBjF+w== X-Received: by 2002:adf:deca:: with SMTP id i10mr4243579wrn.312.1549662038024; Fri, 08 Feb 2019 13:40:38 -0800 (PST) Received: from [192.168.0.107] (79-100-158-105.ip.btc-net.bg. [79.100.158.105]) by smtp.gmail.com with ESMTPSA id v6sm6297728wrd.88.2019.02.08.13.40.36 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Fri, 08 Feb 2019 13:40:37 -0800 (PST) Subject: Re: [PATCH net-next] ipmr: ip6mr: Create new sockopt to clear mfc cache or vifs To: nicolas.dichtel@6wind.com, Callum Sinclair , davem@davemloft.net, kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <20190208041103.31299-1-callum.sinclair@alliedtelesis.co.nz> <20190208041103.31299-2-callum.sinclair@alliedtelesis.co.nz> <5597e8bc-c23e-1f59-0442-260a7b4ca83d@cumulusnetworks.com> <31a5155c-ce6e-4c0f-61c0-35a5472549aa@6wind.com> From: Nikolay Aleksandrov Message-ID: <31565295-16d2-89b5-0e35-8852c49345ec@cumulusnetworks.com> Date: Fri, 8 Feb 2019 23:40:35 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <31a5155c-ce6e-4c0f-61c0-35a5472549aa@6wind.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On 08/02/2019 17:08, Nicolas Dichtel wrote: > Le 08/02/2019 à 15:43, Nikolay Aleksandrov a écrit : >> On 08/02/2019 16:18, Nicolas Dichtel wrote: >>> Le 08/02/2019 à 05:11, Callum Sinclair a écrit : >>>> Currently the only way to clear the mfc cache was to delete the entries >>> mfc stands for 'multicast forwarding cache', so 'mfc cache' is a bit strange. >>> >>>> one by one using the MRT_DEL_MFC socket option or to destroy and >>>> recreate the socket. >>> Note that if entries were added with MRT_ADD_MFC_PROXY, they will survive to the >>> socket destruction. This is not the case with your new cmd. Is it intended? >> >> I think you're referring to MFC_STATIC entries (sk != mroute_sk). It >> doesn't matter how you add an entry - they all get cleaned up if added >> through the mroute socket. > Yes, right. > MRT_FLUSH_MFC_STATIC ? > Sounds good to me.