All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jpirko@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, bhutchings@solarflare.com,
	shemminger@vyatta.com, matt@ozlabs.org
Subject: Re: [Q/RFC] BPF use in broader scope
Date: Thu, 29 Mar 2012 10:31:49 +0200	[thread overview]
Message-ID: <20120329083149.GD2098@minipsycho> (raw)
In-Reply-To: <1333008145.2325.275.camel@edumazet-glaptop>

Thu, Mar 29, 2012 at 10:02:25AM CEST, eric.dumazet@gmail.com wrote:
>On Thu, 2012-03-29 at 09:54 +0200, Jiri Pirko wrote:
>
>> Yep, I'm aware. I must admit that the JIT code scares me a litte :(
>> 
>
>If you add a new XOR instruction in interpreter only, JIT compiler will
>automatically aborts, so no risk.
>
>Each arch maintainer will add the support for the new instructions as
>separate patches.
>
>So you can focus on net/core/filter.c file only.
>

Ok - I can do this for 2). But for 3) JITs need to be modified. So I
would like to kindly ask you and Matt if you can do this modification so
bpf_func takes pointer to mem (scratch store) as second parameter. I'm
sure it's very easy for you to do.

Ccing Matt.

Thanks.

>
>

  reply	other threads:[~2012-03-29  8:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  7:44 [Q/RFC] BPF use in broader scope Jiri Pirko
2012-03-29  7:49 ` David Miller
2012-03-29  7:54   ` Jiri Pirko
2012-03-29  8:02     ` Eric Dumazet
2012-03-29  8:31       ` Jiri Pirko [this message]
2012-03-29  8:43         ` David Miller
2012-03-29  8:45         ` Eric Dumazet
2012-03-29  9:31           ` Jiri Pirko
2012-05-11  2:41             ` Li Yu
2012-05-11  6:22               ` Jiri Pirko
2012-05-11  7:06                 ` Li Yu
2012-05-11  8:45                   ` Jiri Pirko
2012-03-29  7:58 ` Eric Dumazet
2012-03-29  9:49 ` Li Yu
2012-03-29 14:04 ` Nuno Martins

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=20120329083149.GD2098@minipsycho \
    --to=jpirko@redhat.com \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=matt@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.