qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: Michael Goldish <mgoldish@redhat.com>
Cc: lmr@redhat.com, autotest@test.kernel.org, qemu-devel@nongnu.org,
	kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC PATCH 01/14] KVM-test: Add a new macaddress pool	algorithm
Date: Tue, 3 Aug 2010 09:34:33 +0800	[thread overview]
Message-ID: <20100803013433.GA2365@z> (raw)
In-Reply-To: <4C45C677.1030606@redhat.com>

On Tue, Jul 20, 2010 at 06:53:27PM +0300, Michael Goldish wrote:
> On 07/20/2010 04:44 PM, Amos Kong wrote:
> > On Tue, Jul 20, 2010 at 01:19:39PM +0300, Michael Goldish wrote:
> >>
> > 
> > Michael,
> > 
> > Thanks for your comments. Let's simplify this method together.

I would produce a v2 later basing on our discussion.


> >>> +    def get_ifname(self, nic_index=0):
> >>> +        """
> >>> +        Return the ifname of tap device for the guest nic.
> >>> +
> >>> +        @param nic_index: Index of the NIC
> >>> +        """
> >>> +
> >>> +        nics = kvm_utils.get_sub_dict_names(self.params, "nics")
> >>> +        nic_name = nics[nic_index]
> >>> +        nic_params = kvm_utils.get_sub_dict(self.params, nic_name)
> >>> +        if nic_params.get("nic_ifname"):
> >>> +            return nic_params.get("nic_ifname")
> >>> +        else:
> >>> +            return "%s_%s_%s" % (nic_params.get("nic_model"),
> >>> +                                 nic_index, self.vnc_port)
> >>
> >> What's the purpose of this string?
> > 
> > Just avoid repeated ifname.  The vnc_port is unique for each VM, nic_index is unique for each nic of one VM.
> 
> self.instance should also be unique, though it's quite long.

qemu can only receive 15 chars as ifname, instance is too long.
if the prefix of two instance are same, the actual ifnames will not be unique.


linux-user/syscall.c:
#define IFNAMSIZ        16

net/tap-linux.c:
int tap_open(...
...
    if (ifname[0] != '\0')
        pstrcpy(ifr.ifr_name, IFNAMSIZ, ifname);
    else
        pstrcpy(ifr.ifr_name, IFNAMSIZ, "tap%d");

  reply	other threads:[~2010-08-03  1:34 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20  1:34 [Qemu-devel] [Autotest][RFC PATCH 00/14] Patchset of network related subtests Amos Kong
2010-07-20  1:34 ` [Qemu-devel] [RFC PATCH 01/14] KVM-test: Add a new macaddress pool algorithm Amos Kong
2010-07-20 10:19   ` Michael Goldish
2010-07-20 13:44     ` Amos Kong
2010-07-20 15:53       ` Michael Goldish
2010-08-03  1:34         ` Amos Kong [this message]
2010-07-27  1:48   ` [Qemu-devel] " Lucas Meneghel Rodrigues
2010-07-20  1:35 ` [Qemu-devel] [RFC PATCH 02/14] KVM Test: Add a function get_interface_name() to kvm_net_utils.py Amos Kong
2010-07-27  2:08   ` Lucas Meneghel Rodrigues
2010-07-28 10:29     ` Michael Goldish
2010-08-03  1:39       ` Amos Kong
2010-07-20  1:35 ` [Qemu-devel] [RFC PATCH 03/14] KVM Test: Add a common ping module for network related tests Amos Kong
2010-07-27 13:01   ` Lucas Meneghel Rodrigues
2010-07-28 11:50     ` Michael Goldish
2010-07-28 13:56       ` Michael Goldish
2010-07-20  1:35 ` [Qemu-devel] [RFC PATCH 04/14] KVM-test: Add a new subtest ping Amos Kong
2010-07-27 13:15   ` [Qemu-devel] " Lucas Meneghel Rodrigues
2010-08-03  1:54     ` Amos Kong
2010-07-20  1:35 ` [Qemu-devel] [RFC PATCH 05/14] KVM-test: Add a subtest jumbo Amos Kong
2010-07-27 14:13   ` [Qemu-devel] " Lucas Meneghel Rodrigues
2010-08-10  7:18     ` [Qemu-devel] Re: [Autotest] " Amos Kong
2010-07-20  1:35 ` [Qemu-devel] [RFC PATCH 06/14] KVM-test: Add basic file transfer test Amos Kong
2010-07-27 14:36   ` Lucas Meneghel Rodrigues
2010-08-10  9:29     ` [Autotest] " Amos Kong
2010-07-20  1:35 ` [Qemu-devel] [RFC PATCH 07/14] KVM-test: Add a subtest of load/unload nic driver Amos Kong
2010-07-28 18:12   ` Lucas Meneghel Rodrigues
2010-07-20  1:35 ` [Qemu-devel] [RFC PATCH 08/14] KVM-test: Add a subtest of nic promisc Amos Kong
2010-07-28 21:35   ` [Qemu-devel] " Lucas Meneghel Rodrigues
2010-08-11  1:34     ` [Qemu-devel] Re: [Autotest] " Amos Kong
2010-07-20  1:36 ` [Qemu-devel] [RFC PATCH 09/14] KVM-test: Add a subtest of multicast Amos Kong
2010-07-28 21:55   ` Lucas Meneghel Rodrigues
2010-07-20  1:36 ` [Qemu-devel] [RFC PATCH 10/14] KVM-test: Add a subtest of pxe Amos Kong
2010-07-28 22:07   ` Lucas Meneghel Rodrigues
2010-08-10  6:11     ` Amos Kong
2010-07-20  1:36 ` [Qemu-devel] [RFC PATCH 11/14] KVM-test: Add a subtest of changing mac address Amos Kong
2010-07-28 22:30   ` Lucas Meneghel Rodrigues
2010-07-20  1:36 ` [Qemu-devel] [RFC PATCH 12/14] KVM-test: Add a subtest of netperf Amos Kong
2010-07-30 16:32   ` Lucas Meneghel Rodrigues
2010-07-20  1:36 ` [Qemu-devel] [RFC PATCH 13/14] KVM-test: Improve vlan subtest Amos Kong
2010-07-20  1:36 ` [Qemu-devel] [RFC PATCH 14/14] KVM-test: Add subtest of testing offload by ethtool Amos Kong
2010-08-02 19:10   ` [Qemu-devel] " Lucas Meneghel Rodrigues
2010-08-10  7:07     ` [Qemu-devel] Re: [Autotest] " Amos Kong
2010-07-20 12:12 ` [Qemu-devel] Re: [Autotest][RFC PATCH 00/14] Patchset of network related subtests Lucas Meneghel Rodrigues
2010-08-02 20:58 ` Lucas Meneghel Rodrigues

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=20100803013433.GA2365@z \
    --to=akong@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@redhat.com \
    --cc=mgoldish@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).