netdev - Re: [PATCH net-next 0/3] swdev: add IPv4 routing offload

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] [day] [month] [year] [list]

Message-Id: <20150104.221723.437611561422283552.davem@davemloft.net>
Date:	Sun, 04 Jan 2015 22:17:23 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	sfeldma@...il.com
Cc:	netdev@...r.kernel.org, jiri@...nulli.us, john.fastabend@...il.com,
	tgraf@...g.ch, jhs@...atatu.com, andy@...yhouse.net,
	roopa@...ulusnetworks.com
Subject: Re: [PATCH net-next 0/3] swdev: add IPv4 routing offload

From: sfeldma@...il.com
Date: Thu,  1 Jan 2015 19:29:18 -0800

> This patch set adds L3 routing offload support for IPv4 routes.  The idea is to
> mirror routes installed in the kernel's FIB down to a hardware switch device to
> offload the data forwarding path for L3.  Only the data forwarding path is
> intercepted.  Control and management of the kernel's FIB remains with the
> kernel.

It looks like the design for this is still under discussion and that
new patches of whatever is decided upon will be forthcoming
eventually.

Can I ask you guys a huge favor?  DO NOT quote the entire patch when
discussing these changes.

The thread for patch #1 was so time consuming to scan and read in
patchwork because you guys did this.

I know it takes a little bit more work to select and delete the patch
content in the quoted area, but you really have to do this because
otherwise it is a huge burden for reviewers trying to follow the
conversation.

Thanks.
--
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