public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexei Starovoitov <ast@fb.com>
To: Shubham Bansal <illusionist.neo@gmail.com>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
	David Miller <davem@davemloft.net>,
	Network Development <netdev@vger.kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	<linux-arm-kernel@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Kees Cook <keescook@chromium.org>, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next v3] arm: eBPF JIT compiler
Date: Sat, 19 Aug 2017 13:48:43 -0700	[thread overview]
Message-ID: <9d77730f-c6a8-b337-599e-5919207a7e0a@fb.com> (raw)
In-Reply-To: <CAHgaXdJnHxu4gJ8ZVFmrmaXyZL1oFkTbz2K___xKLQedTLmBQg@mail.gmail.com>

On 8/19/17 12:59 PM, Shubham Bansal wrote:
> not be able to compare them like kees this week.
> Does that sound good?

yeah. that's fine. I was more interested in selftests/.../test_progs
numbers before/after, since they're more representative of real world
performance vs test_bpf.ko

> Thats right. But still an improvement I guess. I think I discussed it
> with Daniel and I thought, I should get this patch reach mainstream
> first then I can improve on it.

agree. To me the patch looks ready to land.

  parent reply	other threads:[~2017-08-19 20:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19  9:20 [PATCH net-next v3] arm: eBPF JIT compiler Shubham Bansal
2017-08-19 19:04 ` Alexei Starovoitov
2017-08-19 19:59   ` Shubham Bansal
2017-08-19 20:02     ` Shubham Bansal
2017-08-19 20:48     ` Alexei Starovoitov [this message]
2017-08-19 21:28       ` Shubham Bansal
2017-08-19 21:46         ` Shubham Bansal
2017-08-20  2:11           ` Alexei Starovoitov
2017-08-20 16:12   ` Shubham Bansal
2017-08-20 22:12 ` Daniel Borkmann
2017-08-20 22:16   ` Shubham Bansal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9d77730f-c6a8-b337-599e-5919207a7e0a@fb.com \
    --to=ast@fb.com \
    --cc=andrew@lunn.ch \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=illusionist.neo@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox