netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: David Miller <davem@davemloft.net>
Cc: nschichan@freebox.fr, dborkman@redhat.com, ast@plumgrid.com,
	mgherzan@gmail.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2] ARM: net: add JIT support for loads from struct seccomp_data.
Date: Sun, 10 May 2015 20:40:28 +0100	[thread overview]
Message-ID: <20150510194028.GA2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150509.222858.26253293963482182.davem@davemloft.net>

On Sat, May 09, 2015 at 10:28:58PM -0400, David Miller wrote:
> From: Nicolas Schichan <nschichan@freebox.fr>
> Date: Thu,  7 May 2015 15:00:13 +0200
> 
> > Signed-off-by: Nicolas Schichan <nschichan@freebox.fr>
> > ---
> > 
> > This patch was first sent as part of a serie modifying the core
> > seccomp code to allow the use of the classic BPF JIT. As the core
> > changes have been submitted to netdev by Daniel Borkmann, it is now
> > time to re-submit this patch separately.
> > 
> > While not physically dependent of the core seccomp changes they are
> > needed for the code added in this patch to be triggered.
> 
> Where would you like this to be applied, my tree?
> 
> This is an ongoing situation, where people have traditionally not
> consistently wanted bpf JIT patches to go into the networking tree.
> 
> So I beg everyone posting such things to netdev to be _clear_
> and _explicit_ about whether you expect me to integrate the patch
> or not.

I think you have taken previous ARM net JIT patches, so I think it
makes sense if you continue to do so.  I'm not knowledgable of the
JIT interface myself, all I can say about many of these patches is
that they look okay to me on a superficial basis.

I suspect you're doing more or less the same, but from a slightly
different perspective (presumably through not knowing ARM assembly.)

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-05-10 19:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 13:00 [PATCH v2] ARM: net: add JIT support for loads from struct seccomp_data Nicolas Schichan
2015-05-10  2:28 ` David Miller
2015-05-10 19:40   ` Russell King - ARM Linux [this message]
2015-05-10 23:20     ` David Miller
2015-05-12 22:20 ` David Miller

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=20150510194028.GA2067@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=ast@plumgrid.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgherzan@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nschichan@freebox.fr \
    /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;
as well as URLs for NNTP newsgroup(s).