linux-kernel - Re: [RFC PATCH v2] bridge: make it possible for packets to traverse the bridge without hitting netfilter

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150306.124930.216237089666857656.davem@davemloft.net>
Date:	Fri, 06 Mar 2015 12:49:30 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	imrep.amz@...il.com
Cc:	imrep@...zon.de, fw@...len.de, bridge@...ts.linux-foundation.org,
	stephen@...workplumber.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, aliguori@...zon.com, nbd@...nwrt.org
Subject: Re: [RFC PATCH v2] bridge: make it possible for packets to
 traverse the bridge without hitting netfilter

From: Imre Palik <imrep.amz@...il.com>
Date: Fri, 06 Mar 2015 11:34:29 +0100

> Removed those pieces of the packet pipeline that I don't necessarily
> need one-by-one.  Then measured their effect on small packet
> performance.
> 
> This was the only part that produced considerable effect.
> 
> The pure speculation was about why the effect is more than 15%
> increase in packet throughput, although the code path avoided
> contains way less code than 15% of the packet pipeline.  It seems,
> Felix Fietkau profiled similar changes, and found my guess well
> founded.

Yes and that's the part being left out, the "why".

That's part of what I expect in the justification.

Look, we're not doing things this way.  We need to find a clean
and generic way to make the netfilter hooks as cheap as possible
when netfilter rules are not in use.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/