Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1716078 > unrolled thread

Re: [PATCH 0/3] MIPS,bpf: Improvements for MIPS eBPF JIT

Started byDavid Miller <davem@davemloft.net>
First post2017-08-21 05:10 +0200
Last post2017-08-21 19:40 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 0/3] MIPS,bpf: Improvements for MIPS eBPF JIT David Miller <davem@davemloft.net> - 2017-08-21 05:10 +0200
    Re: [PATCH 0/3] MIPS,bpf: Improvements for MIPS eBPF JIT Daniel Borkmann <daniel@iogearbox.net> - 2017-08-21 10:30 +0200
      Re: [PATCH 0/3] MIPS,bpf: Improvements for MIPS eBPF JIT David Miller <davem@davemloft.net> - 2017-08-21 19:40 +0200

#1716078 — Re: [PATCH 0/3] MIPS,bpf: Improvements for MIPS eBPF JIT

FromDavid Miller <davem@davemloft.net>
Date2017-08-21 05:10 +0200
SubjectRe: [PATCH 0/3] MIPS,bpf: Improvements for MIPS eBPF JIT
Message-ID<ugLgd-7f3-3@gated-at.bofh.it>
From: David Daney <david.daney@cavium.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?

If the dependency is on MIPS changes, then if I cannot apply this as
it will break the net-next build on MIPS.  You should merge this
via the MIPS tree, where the dependencies are, in that case.

Please clarify what is specifically happening here.

Thanks.

[toc] | [next] | [standalone]


#1716174

FromDaniel Borkmann <daniel@iogearbox.net>
Date2017-08-21 10:30 +0200
Message-ID<ugQfT-1Uf-1@gated-at.bofh.it>
In reply to#1716078
On 08/21/2017 05:06 AM, David Miller wrote:
> From: David Daney <david.daney@cavium.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.

Thanks,
Daniel

[toc] | [prev] | [next] | [standalone]


#1716750

FromDavid Miller <davem@davemloft.net>
Date2017-08-21 19:40 +0200
Message-ID<ugYQa-7jc-21@gated-at.bofh.it>
In reply to#1716174
From: Daniel Borkmann <daniel@iogearbox.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@cavium.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.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web