[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH net-next v4] xen-netfront: delay gARP until backend switches to Connected

On 01/02/12 15:50, Jan Beulich wrote:

Wouldn't all of this equally apply to the 2.6.18 kernel and its derivates?

I haven't checked the linux-2.6.18-xen.hg source at all before because the (first) affected RHEL-5 netfront patch ("linux-2.6-xen-xennet-coordinate-ARP-with-backend-network-status.patch") states,

    The frontend part of the patch is not applicable in upstream
    Linux as there is no gratuitous ARP packet support there at all.
    While the backend upstream is dead as far as I know.  So this
    is RHEL5-specific.

Regarding the RHEL-5 host side,

>> (1) ensure that the backend only moves to Connected xenbus state
>> after its hotplug scripts completed, ie. the netback interface got
>> added to the bridge; and

>> Sub-condition (1) is already satisfied by commit f942dc2552b8 in
>> Linus' tree, based on commit 6b0b80ca7165 from [1].

>> [1] git://xenbits.xen.org/people/ianc/linux-2.6.git#upstream/dom0/backend/netback-history

I figured the backend change is "already upstream". (Actually where I took it from was 43223efd9bfd in Jeremy's tree.)

So, what do you want me to do? I think I could get the frontend patch right without compiling linux-2.6.18-xen.hg. The backend is more messy however.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.