Re: [IPoIB] Identify multicast packets and fix IGMP breakage V3
From: David Miller <hidden>
Date: 2010-08-27 00:07:16
Also in:
linux-rdma
Possibly related (same subject, not in this thread)
- 2010-09-28 · Re: [IPoIB] Identify multicast packets and fix IGMP breakage V3 · Roland Dreier <hidden>
- 2010-09-14 · Re: [IPoIB] Identify multicast packets and fix IGMP breakage V3 · Christoph Lameter <hidden>
- 2010-09-14 · Re: [IPoIB] Identify multicast packets and fix IGMP breakage V3 · Or Gerlitz <hidden>
- 2010-08-27 · Re: [IPoIB] Identify multicast packets and fix IGMP breakage V3 · Christoph Lameter <hidden>
- 2010-08-27 · Re: [IPoIB] Identify multicast packets and fix IGMP breakage V3 · Jason Gunthorpe <hidden>
From: Christoph Lameter <redacted> Date: Thu, 26 Aug 2010 18:57:09 -0500 (CDT)
On Thu, 26 Aug 2010, Jason Gunthorpe wrote:quoted
I think doing the memcmp only in the multicast path should be reasonable overhead wise.Thats is not always possible. Here the multicast path is the default path that is taken 99% of the time.
The highest cost is bringing in that packet header's cache line, which you've already done by reading the byte and checking for 0xff. I doubt the memcmp() can possibly matter. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html