[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170821.103203.824546849038094695.davem@davemloft.net>
Date: Mon, 21 Aug 2017 10:32:03 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: daniel@...earbox.net
Cc: david.daney@...ium.com, ast@...nel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org,
ralf@...ux-mips.org
Subject: Re: [PATCH 0/3] MIPS,bpf: Improvements for MIPS eBPF JIT
From: Daniel Borkmann <daniel@...earbox.net>
Date: Mon, 21 Aug 2017 10:24:23 +0200
> On 08/21/2017 05:06 AM, David Miller wrote:
>> From: David Daney <david.daney@...ium.com>
>> Date: Fri, 18 Aug 2017 16:40:30 -0700
>>
>>> I suggest that the whole thing go via the BPF/net-next path as there
>>> are dependencies on code that is not yet merged to Linus' tree.
>>
>> What kind of dependency? On networking or MIPS changes?
>
> On networking, David implemented the JLT, JLE, JSLT and JSLE
> ops for the JIT in the patch set. Back then the MIPS JIT wasn't
> in net-next tree, thus this is basically just a follow-up, so
> that we have all covered with JIT support for net-next.
Ok, that makes sense, thanks for explaining.
Powered by blists - more mailing lists