On Thu, 2014-07-10 at 12:46 +0200, Tom Gundersen wrote:

On Thu, Jul 10, 2014 at 11:01 AM, Ian Campbell [off-list ref] wrote:

quoted

On Thu, 2014-07-10 at 10:17 +0200, Tom Gundersen wrote:

quoted

The name contains then xen handle, which is not guaranteed to be
stable between restarts, so label this NET_NAME_ENUM.

FWIW the N'th interface for domain with domid D will always be named
vifD.N.

If you reboot domain D then it's domid will change to E and the new
device will be vifE.N.

I don't know if that counts as predictable as far as the interface you
are introducing is concerned.

That was my understanding, thanks for confirming.

The idea is that the same interface on the same machine must get the
same name between reboots in order to be considered predictable. So
under the assumption that a rebooted domain should be considered "the
same machine" (i.e., it still has the same local configuration,
possibly referencing the interface names), then we should consider the
names not predictable, so NET_NAME_ENUM.

OK, thanks. I'll defer to you understanding of what this interface is
supposed to mean: Acked-by: Ian Campbell [off-list ref]

Ian.