[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YFeso1fr1hLxi3lR@lunn.ch>
Date: Sun, 21 Mar 2021 21:29:23 +0100
From: Andrew Lunn <andrew@...n.ch>
To: "Hsu, Chiahao" <andyhsu@...zon.com>
Cc: Leon Romanovsky <leon@...nel.org>, netdev@...r.kernel.org,
wei.liu@...nel.org, paul@....org, davem@...emloft.net,
kuba@...nel.org, xen-devel@...ts.xenproject.org
Subject: Re: [net-next 1/2] xen-netback: add module parameter to disable
ctrl-ring
> > At the end, it will be more granular module parameter that user still
> > will need to guess.
> I believe users always need to know any parameter or any tool's flag before
> they use it.
> For example, before user try to set/clear this ctrl_ring_enabled, they
> should already have basic knowledge about this feature,
> or else they shouldn't use it (the default value is same as before), and
> that's also why we use the 'ctrl_ring_enabled' as parameter name.
To me, it seems you are fixing this problem in the wrong place. As a
VM user in the cloud, i have no idea how the cloud provider needs the
VM configured to allow the cloud provider to migrate the VM to
somewhere else in the bitbarn. As the VM user, it should not be my
problem. I would expect the cloud provider to configure the VM host to
only expose facilities to the VM which allows it to be migrated.
This is a VM host problem, not a VM problem.
Andrew
Powered by blists - more mailing lists