netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Axtens <dja@axtens.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, shannon.nelson@oracle.com
Subject: Re: [PATCH] macvlan: verify MTU before lowerdev xmit
Date: Fri, 17 Nov 2017 23:18:25 +1100	[thread overview]
Message-ID: <87y3n5f69a.fsf@linkitivity.dja.id.au> (raw)
In-Reply-To: <20171117.174131.854361434090179436.davem@davemloft.net>

Hi Dave,

> So how exactly do the oversized packets get to the macvlan device from
> the VM in this scenerio?  That detail seems to be missing from the
> diagrams you provided earlier.  The VM and the macvlan boxes are just
> connected with a line.

Inside the VM I'm using netperf talking on an interface which the guest
believes to have a MTU of 1500.

I'm setting up the VM using libvirt - my understanding is that libvirt
creates a macvtap device in private mode, and qemu opens that tap device
and writes data from the emulated network card (I see the same behaviour
with a emulated rtl8139, e1000, and with virtio).

I think I could replicate this with any userspace program - qemu is just
the easiest for me at the moment.

Hopefully that's what you had in mind? Let me know if you wanted
different info.

Regards,
Daniel

[The gory details, in case it matters: The VM has a network adaptor with
the following XML:

    <interface type='direct'>
      <mac address='52:54:00:e7:a2:ac'/>
      <source dev='enx0050b6655ff2' mode='private'/>
      <model type='rtl8139'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </interface>
]

>
> Thank you.

      reply	other threads:[~2017-11-17 12:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 10:32 [PATCH] macvlan: verify MTU before lowerdev xmit Daniel Axtens
2017-11-14 17:03 ` Shannon Nelson
2017-11-14 19:06   ` Shannon Nelson
2017-11-15  3:27     ` Daniel Axtens
2017-11-17  5:54 ` David Miller
2017-11-17  8:34   ` Daniel Axtens
2017-11-17  8:41     ` David Miller
2017-11-17 12:18       ` Daniel Axtens [this message]

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=87y3n5f69a.fsf@linkitivity.dja.id.au \
    --to=dja@axtens.net \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shannon.nelson@oracle.com \
    /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).