[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170314.173645.1126342566528886979.davem@davemloft.net>
Date: Tue, 14 Mar 2017 17:36:45 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: ddaney@...iumnetworks.com
Cc: david.daney@...ium.com, ralf@...ux-mips.org,
linux-mips@...ux-mips.org, james.hogan@...tec.com, ast@...nel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
steven.hill@...ium.com
Subject: Re: [PATCH v2 0/5] MIPS: BPF: JIT fixes and improvements.
From: David Daney <ddaney@...iumnetworks.com>
Date: Tue, 14 Mar 2017 17:34:02 -0700
> On 03/14/2017 05:29 PM, David Miller wrote:
>> From: David Daney <david.daney@...ium.com>
>> Date: Tue, 14 Mar 2017 14:21:39 -0700
>>
>>> Changes from v1:
>>>
>>> - Use unsigned access for SKF_AD_HATYPE
>>>
>>> - Added three more patches for other problems found.
>>>
>>>
>>> Testing the BPF JIT on Cavium OCTEON (mips64) with the test-bpf module
>>> identified some failures and unimplemented features.
>>>
>>> With this patch set we get:
>>>
>>> test_bpf: Summary: 305 PASSED, 0 FAILED, [85/297 JIT'ed]
>>>
>>> Both big and little endian tested.
>>>
>>> We still lack eBPF support, but this is better than nothing.
>>
>> What tree are you targetting with these changes? Do you expect
>> them to go via the MIPS or the net-next tree?
>>
>> Please be explicit about this in the future.
>>
>
> Sorry I didn't mention it.
>
> My expectation is that Ralf would merge it via the MIPS tree, as it is
> fully contained within arch/mips/*
Great, thanks for letting me know.
Powered by blists - more mailing lists