[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMhqHbHDH06O5+Y_2mNQM3BNVA9bCLBS70ZK+=-6upDtaA@mail.gmail.com>
Date: Tue, 16 Feb 2016 21:30:18 +0200
From: Or Gerlitz <gerlitz.or@...il.com>
To: John Fastabend <john.fastabend@...il.com>
Cc: Amir Vadai <amir@...ai.me>, Jamal Hadi Salim <jhs@...atatu.com>,
David Miller <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
Jiří Pírko <jiri@...nulli.us>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Subject: Re: [net-next PATCH v2 0/8] tc offload for cls_u32 on ixgbe
On Tue, Feb 16, 2016 at 8:00 AM, John Fastabend
<john.fastabend@...il.com> wrote:
[...]
> Specifically this uses a 'big hammer' feature bit
> to do the offload or not. If the bit is set you get offloaded rules
> if it is not then rules will not be offloaded. If we can agree on
> this patch series there are some more patches on my queue we can
> talk about to make the offload decision per rule using flags similar
> to how we do l2 mac updates. Additionally the error strategy can
> be improved to be hard aborting, log and continue, etc. I think
> these are nice to have improvements but shouldn't block this series.
John,
I thought we've got into agreement in netdev that the offloading
directive would be a tri-state creature (sw, hw and fail the op if
can't, hw and fallback to sw). Can you please elaborate what do you
mean by "make the offload decision per rule using flags similar to how
we do l2 mac updates"
Or.
Powered by blists - more mailing lists