| 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
| ||
|
Message-Id: <20150302.154021.291909338132330257.davem@davemloft.net> Date: Mon, 02 Mar 2015 15:40:21 -0500 (EST) From: David Miller <davem@...emloft.net> To: roopa@...ulusnetworks.com Cc: sfeldma@...il.com, netdev@...r.kernel.org, jiri@...nulli.us Subject: Re: [PATCH net-next v2 4/4] switchdev: don't support custom ip rules, for now From: roopa <roopa@...ulusnetworks.com> Date: Mon, 02 Mar 2015 11:09:32 -0800 > On 3/2/15, 9:00 AM, Scott Feldman wrote: >> On Mon, Mar 2, 2015 at 6:36 AM, roopa <roopa@...ulusnetworks.com> >> wrote: >>> On 3/2/15, 2:06 AM, sfeldma@...il.com wrote: >>>> From: Scott Feldman <sfeldma@...il.com> >>>> >>>> Keep switchdev FIB offload model simple for now and don't allow custom >>>> ip >>>> rules. >>>> >>>> Signed-off-by: Scott Feldman <sfeldma@...il.com> >>> >>> I don't see a need to do this. And seems very aggressive. >>> Also, note that the rules in a system can be on non-hw accelerated >>> ports. >> It is aggressive but it's the safest choice for the first pass on this >> L3 offload. Without, switchdev has no way to model custom ip rules >> down to hardware. Let's start with this aggressive case, and that'll >> force us to work on relaxing it. >> >> > But, this will not allow hw acceleration of routes even if you had a > rule for the management traffic for example. We start simple, add complexity later. -- 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