[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADvbK_ftDf_AsbEeF9EViBm68Co3bj1L-fR1-BDA0Uxn=1LPpA@mail.gmail.com>
Date: Thu, 3 Apr 2014 13:28:33 +0800
From: lucien xin <lucien.xin@...il.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: David Miller <davem@...emloft.net>,
network dev <netdev@...r.kernel.org>
Subject: Re: [PATCH] vxlan: using AF_PACKET socket to send multicast packet
cause WARNING
On Wed, Apr 2, 2014 at 10:51 PM, Stephen Hemminger
<stephen@...workplumber.org> wrote:
> That breaks local socket accounting for tunneled packets.
It do break, I think it should break, becaue vlxan send UDP packets,
it should be bound to UDP socket.
after encapsulating the packet with local socket. it reach the
vxlan's xmit. and It should be take into
vxlan's UDP socket.and local socket should not take care of it.
now the problem is that the local socket(AF_PACKET) cannot take it to
travel the ipv4/6 protocol stack,
unlike TCP/UDP socket. perhaps, in later, there will be other type
protocol family that has the same issue.
so I think vxlan should support it.
> The idea is that a TCP socket sending over vxlan will keep it's
> memory accounting all the way until the device sends it.
yes, the idea is there. But if vxlan is treated as net_device, the
packet enter it's xmit(), which seems
to be send by the device. so when the packet goes there, the TCP
socket also should let it go.
of course, if you insist the idea you said, to support only some type
protocol family, do you have some
better suggestion?
I cannot be sure I understand you well, those are just my own
thoughts. pls help to check and correct it . :)
many thanks to your reply.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists