Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752700AbaBMEf4 (ORCPT ); Wed, 12 Feb 2014 23:35:56 -0500 Received: from mail-la0-f43.google.com ([209.85.215.43]:62012 "EHLO mail-la0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751427AbaBMEfy (ORCPT ); Wed, 12 Feb 2014 23:35:54 -0500 MIME-Version: 1.0 In-Reply-To: References: <1392071391-13215-1-git-send-email-mcgrof@do-not-panic.com> <1392071391-13215-3-git-send-email-mcgrof@do-not-panic.com> <1392108205.22033.16.camel@dagon.hellion.org.uk> <1392203708.13563.50.camel@kazak.uk.xensource.com> From: "Luis R. Rodriguez" Date: Wed, 12 Feb 2014 20:35:31 -0800 X-Google-Sender-Auth: DE-lUQMCyNalPjJf3BidnR7jo08 Message-ID: Subject: Re: [RFC 2/2] xen-netback: disable multicast and use a random hw MAC address To: Ian Campbell Cc: "netdev@vger.kernel.org" , xen-devel@lists.xenproject.org, Paul Durrant , Wei Liu , kvm@vger.kernel.org, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 12, 2014 at 8:27 PM, Luis R. Rodriguez wrote: > I have a test patch that now works that restricts xen-netback from > getting any IPv4 and IPv6 addresses, and disables multicast. With this > set in place the xen-frontend still gets IPv4 and IPv6 addresses and > Multicast still works. This was tested under a shared physical > environment, I'll have to test NAT next, and also see if we can enable > this as an option for KVM for their TAP 'backend' interfaces. Also perhaps a silly question, as I haven't yet looked carefully into the qemu TAP usage / requirement yet, but has anyone considered just having a dma-buf agent for us in userspace ? That'd remove any redundant interfaces and do let qemu do DMA directly. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/