From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: dev@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-dev] [PATCH 0/2] bpf: fix x86 jit issue
Date: Thu, 8 Nov 2018 12:36:42 +0000 [thread overview]
Message-ID: <1541680604-17245-1-git-send-email-konstantin.ananyev@intel.com> (raw)
*** BLURB HERE ***
Konstantin Ananyev (2):
bpf: fix x86 jit for immediate loads
test/bpf: add test for immediate load
lib/librte_bpf/bpf_jit_x86.c | 28 ++++++---
test/test/test_bpf.c | 108 +++++++++++++++++++++++++++++++++++
2 files changed, 128 insertions(+), 8 deletions(-)
--
2.17.1
next reply other threads:[~2018-11-08 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 12:36 Konstantin Ananyev [this message]
2018-11-08 12:36 ` [dpdk-dev] [PATCH 1/2] bpf: fix x86 jit for immediate loads Konstantin Ananyev
2018-11-08 12:36 ` [dpdk-dev] [PATCH 2/2] test/bpf: add test for immediate load Konstantin Ananyev
2018-11-13 22:21 ` [dpdk-dev] [PATCH 0/2] bpf: fix x86 jit issue Thomas Monjalon
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=1541680604-17245-1-git-send-email-konstantin.ananyev@intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.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).