All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sridhar Samudrala <sri@us.ibm.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: No iproute2 for 2.6.38
Date: Tue, 15 Mar 2011 22:46:37 -0700	[thread overview]
Message-ID: <4D804EBD.4030904@us.ibm.com> (raw)
In-Reply-To: <20110315195534.0cc43032@nehalam>

On 3/15/2011 7:55 PM, Stephen Hemminger wrote:
> I am not going to bother releasing for 2.6.38 the only changes
> were later reverted.
2.6.38 includes support for macvlan/macvtap 'passthru' mode that allows 
assigning
SR-IOV VFs to a KVM guest via macvtap/virtio.
It is not possible to support live migration using direct assignment of 
VF's to a guest,
but 'passthu' assignment makes this possible.

Enabling this feature requires the following patch to iproute2 that 
allows creating macvlan
device in 'passthru' mode.
     http://patchwork.ozlabs.org/patch/69515/
Looks like this patch is still marked as 'Awaiting upstream'.

Could you apply this patch and it would be great if a version of 
iproute2 is released for 2.6.38.

Thanks
Sridhar

> ---
> Roopa Prabhu (1):
>        iproute2: add VF_PORT support
>
> Stephen Hemminger (3):
>        Update to lasest kernel headers
>        Revert "iproute2: add VF_PORT support"
>        v2.6.38
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2011-03-16  5:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16  2:55 No iproute2 for 2.6.38 Stephen Hemminger
2011-03-16  5:46 ` Sridhar Samudrala [this message]
2011-03-17  0:04   ` Stephen Hemminger
2011-03-17 14:14     ` Henrique de Moraes Holschuh
2011-03-17 15:12       ` David Miller

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=4D804EBD.4030904@us.ibm.com \
    --to=sri@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.