From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: netdev@vger.kernel.org,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Matt Evans <matt@ozlabs.org>
Subject: Re: [RFC PATCH 0/1] BPF JIT for PPC64
Date: Sat, 25 Jun 2011 09:33:31 +1000 [thread overview]
Message-ID: <1308958411.32158.335.camel@pasglop> (raw)
In-Reply-To: <750BF3E9-A788-4302-8AA1-4630614E20DC@kernel.crashing.org>
On Fri, 2011-06-24 at 04:16 -0500, Kumar Gala wrote:
> > Tested in-situ (tcpdump with varying complexity filters) and with a random BPF
> > generator; I haven't verified loads from the fall back skb_copy_bits path. Bug
> > reports/testing would be very welcome.
>
> Would be nice to get PPC32 support as well.
Patches welcome :-)
Cheers,
Ben.
prev parent reply other threads:[~2011-06-24 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 6:02 [RFC PATCH 0/1] BPF JIT for PPC64 Matt Evans
2011-06-24 9:16 ` Kumar Gala
2011-06-24 23:33 ` Benjamin Herrenschmidt [this message]
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=1308958411.32158.335.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matt@ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).