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=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_PASS autolearn=ham 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 B1433C10F00 for ; Thu, 21 Mar 2019 16:31:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 802D021A4A for ; Thu, 21 Mar 2019 16:31:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=oracle.com header.i=@oracle.com header.b="MuYsWwZM" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728592AbfCUQb5 (ORCPT ); Thu, 21 Mar 2019 12:31:57 -0400 Received: from userp2120.oracle.com ([156.151.31.85]:51192 "EHLO userp2120.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726787AbfCUQb4 (ORCPT ); Thu, 21 Mar 2019 12:31:56 -0400 Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x2LGQLNc103744; Thu, 21 Mar 2019 16:31:45 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=corp-2018-07-02; bh=AmbrHqdl8vbEcYbuCQngzG//TwEYafwLQGLTGDF8qYQ=; b=MuYsWwZMgtOtYEHUEHY+5DRNqNvT++mk3J6De5iO1n2xrr6RD4AOs8y9awGFTu4luK42 s+n2gAQXxLcqpZnyA3/50ARVPx4oRpLpd4HO2w200o5IzEiBS3y2yHLGKtITqudSd5ob 5kYxNRXAxqHgYeslvZYViqEM2FlR5vftZu0PF1P9Gfd5sKObQmO4BtIbGFJvgV3Gzy4W qn8mPeuwXKohaUforqkhJlycJvHJSD3HwvEo8owbZ27K1sOTpOIXmjYzgVMPRlyhCqOp UBRpTPYCUd5o18oGMlzDSlwZXb2wAbNG6X43Q9uYO5I5JiychwiuwV94srM4hWGAbcGZ pg== Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by userp2120.oracle.com with ESMTP id 2r8ssrsdge-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 21 Mar 2019 16:31:44 +0000 Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id x2LGVgP9015948 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 21 Mar 2019 16:31:43 GMT Received: from abhmp0016.oracle.com (abhmp0016.oracle.com [141.146.116.22]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id x2LGVfM5023927; Thu, 21 Mar 2019 16:31:41 GMT Received: from [10.30.3.18] (/213.57.127.2) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 21 Mar 2019 09:31:41 -0700 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: [summary] virtio network device failover writeup From: Liran Alon In-Reply-To: <20190321114557-mutt-send-email-mst@kernel.org> Date: Thu, 21 Mar 2019 18:31:35 +0200 Cc: Stephen Hemminger , Si-Wei Liu , Sridhar Samudrala , Alexander Duyck , Jakub Kicinski , Jiri Pirko , David Miller , Netdev , virtualization@lists.linux-foundation.org, boris.ostrovsky@oracle.com, vijay.balakrishna@oracle.com, jfreimann@redhat.com, ogerlitz@mellanox.com, vuhuong@mellanox.com Content-Transfer-Encoding: quoted-printable Message-Id: References: <36772E22-7A8F-4C42-A731-398E3204B418@oracle.com> <20190320180641-mutt-send-email-mst@kernel.org> <20190321044920-mutt-send-email-mst@kernel.org> <20190321082532-mutt-send-email-mst@kernel.org> <20190321085159-mutt-send-email-mst@kernel.org> <2939FB15-720A-4C9E-92B7-2DBA139DDE0F@oracle.com> <20190321084517.773a65fa@shemminger-XPS-13-9360> <20190321114557-mutt-send-email-mst@kernel.org> To: "Michael S. Tsirkin" X-Mailer: Apple Mail (2.3445.4.7) X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9202 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903210116 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > On 21 Mar 2019, at 17:50, Michael S. Tsirkin wrote: >=20 > On Thu, Mar 21, 2019 at 08:45:17AM -0700, Stephen Hemminger wrote: >> On Thu, 21 Mar 2019 15:04:37 +0200 >> Liran Alon wrote: >>=20 >>>>=20 >>>> OK. Now what happens if master is moved to another namespace? Do we = need >>>> to move the slaves too? =20 >>>=20 >>> No. Why would we move the slaves? The whole point is to make most = customer ignore the net-failover slaves and remain them =E2=80=9Chidden=E2= =80=9D in their dedicated netns. >>> We won=E2=80=99t prevent customer from explicitly moving the = net-failover slaves out of this netns, but we will not move them out of = there automatically. >>=20 >>=20 >> The 2-device netvsc already handles case where master changes = namespace. >=20 > Is it by moving slave with it? See c0a41b887ce6 ("hv_netvsc: move VF to same namespace as netvsc = device=E2=80=9D). It seems that when NetVSC master netdev changes netns, the VF is moved = to the same netns by the NetVSC driver. Kinda the opposite than what we are suggesting here to make sure that = the net-failover master netdev is on a separate netns than it=E2=80=99s slaves... -Liran >=20 > --=20 > MST