netdev - Re: [Q/RFC] BPF use in broader scope

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120329093158.GA2275@minipsycho.brq.redhat.com>
Date:	Thu, 29 Mar 2012 11:31:58 +0200
From:	Jiri Pirko <jpirko@...hat.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	bhutchings@...arflare.com, shemminger@...tta.com, matt@...abs.org
Subject: Re: [Q/RFC] BPF use in broader scope

Thu, Mar 29, 2012 at 10:45:32AM CEST, eric.dumazet@...il.com wrote:
>On Thu, 2012-03-29 at 10:31 +0200, Jiri Pirko wrote:
>> Thu, Mar 29, 2012 at 10:02:25AM CEST, eric.dumazet@...il.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.
>
>I am not sure why you want this.
>
>This adds register pressure (at least for x86) ...

Well I think that there would become handy to be able to pass some data
to bpf_func (other than skb). But it's just an idea.

>
>
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html