[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150408.231456.1063648455572594170.davem@davemloft.net>
Date: Wed, 08 Apr 2015 23:14:56 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: ast@...mgrid.com
Cc: daniel@...earbox.net, tgraf@...g.ch, jiri@...nulli.us,
jhs@...atatu.com, netdev@...r.kernel.org
Subject: Re: [PATCH v3 net-next 2/2] tc: add 'needs_l2' flag to ingress
qdisc
From: Alexei Starovoitov <ast@...mgrid.com>
Date: Wed, 08 Apr 2015 20:05:13 -0700
> I'm sure there is a way to propagate the offset into the programs.
> It's not about efficiency of programs, but about consistency.
> Programs should know nothing about kernel. Sending network offset
> into them is exposing this very specific kernel behavior.
It can be performed by the data access helpers the JIT'd programs
have to invoke anyways.
--
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