From: Thomas Monjalon <thomas@monjalon.net>
To: Ophir Munk <ophirmu@mellanox.com>
Cc: dev@dpdk.org, Pascal Mazon <pascal.mazon@6wind.com>,
Olga Shern <olgas@mellanox.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Viktorin <viktorin@rehivetech.com>,
Jianbo Liu <jianbo.liu@arm.com>
Subject: Re: [PATCH v1] net/tap: add eBPF ARM and POWERPC architectures support
Date: Wed, 31 Jan 2018 15:28:55 +0100 [thread overview]
Message-ID: <5755586.fHBMFWOpR3@xps> (raw)
In-Reply-To: <1517406286-4306-1-git-send-email-ophirmu@mellanox.com>
31/01/2018 14:44, Ophir Munk:
> This commit adds eBPF system call definitions for ARM and POWERPC
> architectures.
> Old Linux header files may not define eBPF system call numbers.
> In order to enable a successful eBPF compilation on all Linux
> platforms - the missing system call definitions are explicitly added.
>
> #elif defined(__powerpc__)
> # define __NR_bpf 361
> #elif defined(__arm__)
> # define __NR_bpf 386
PowerPC is already added on master branch.
prev parent reply other threads:[~2018-01-31 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 13:44 [PATCH v1] net/tap: add eBPF ARM and POWERPC architectures support Ophir Munk
2018-01-31 14:28 ` Thomas Monjalon [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=5755586.fHBMFWOpR3@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianbo.liu@arm.com \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=pascal.mazon@6wind.com \
--cc=viktorin@rehivetech.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.