From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: netdev@vger.kernel.org, jakub.kicinski@netronome.com,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
mchan@broadcom.com, John Fastabend <john.fastabend@gmail.com>,
peter.waskiewicz.jr@intel.com,
Daniel Borkmann <borkmann@iogearbox.net>,
Andy Gospodarek <andy@greyhouse.net>,
brouer@redhat.com
Subject: Re: [net-next V2 PATCH 5/5] samples/bpf: add cpumap sample program xdp_redirect_cpu
Date: Mon, 2 Oct 2017 14:07:23 +0200 [thread overview]
Message-ID: <20171002140723.7667a9b4@redhat.com> (raw)
In-Reply-To: <20170930030607.sk2wzjxxlbhkkt7k@ast-mbp>
On Fri, 29 Sep 2017 20:06:09 -0700
Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> > +/*** Trace point code ***/
> > +
> > +/* Tracepoint format: /sys/kernel/debug/tracing/events/xdp/xdp_redirect/format
> > + * Code in: kernel/include/trace/events/xdp.h
> > + */
> > +struct xdp_redirect_ctx {
> > + unsigned short common_type; // offset:0; size:2; signed:0;
> > + unsigned char common_flags; // offset:2; size:1; signed:0;
> > + unsigned char common_preempt_count;// offset:3; size:1; signed:0;
> > + int common_pid; // offset:4; size:4; signed:1;
>
> this part is not right. First 8 bytes are not accessible by bpf code.
> Please use __u64 pad; or similar here.
I've corrected this in V3.
Can you explain why BPF cannot access these (first 8 bytes) struct members?
> Just noticed that samples/bpf/xdp_monitor_kern.c has the same problem.
>
> > +
> > + int prog_id; // offset:8; size:4; signed:1;
> > + u32 act; // offset:12 size:4; signed:0;
> > + int ifindex; // offset:16 size:4; signed:1;
> > + int err; // offset:20 size:4; signed:1;
> > + int to_ifindex; // offset:24 size:4; signed:1;
> > + u32 map_id; // offset:28 size:4; signed:0;
> > + int map_index; // offset:32 size:4; signed:1;
> > +}; // offset:36
>
> the second part of fields is correct.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2017-10-02 12:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 16:34 [net-next V2 PATCH 0/5] New bpf cpumap type for XDP_REDIRECT Jesper Dangaard Brouer
2017-09-29 16:34 ` [net-next V2 PATCH 1/5] bpf: introduce new bpf cpu map type BPF_MAP_TYPE_CPUMAP Jesper Dangaard Brouer
2017-09-29 18:41 ` Jakub Kicinski
2017-09-29 19:58 ` Jesper Dangaard Brouer
2017-09-29 16:34 ` [net-next V2 PATCH 2/5] bpf: XDP_REDIRECT enable use of cpumap Jesper Dangaard Brouer
2017-10-01 0:13 ` kbuild test robot
2017-09-29 16:34 ` [net-next V2 PATCH 3/5] bpf: cpumap xdp_buff to skb conversion and allocation Jesper Dangaard Brouer
2017-09-29 16:34 ` [net-next V2 PATCH 4/5] bpf: cpumap add tracepoints Jesper Dangaard Brouer
2017-09-29 16:34 ` [net-next V2 PATCH 5/5] samples/bpf: add cpumap sample program xdp_redirect_cpu Jesper Dangaard Brouer
2017-09-30 3:06 ` Alexei Starovoitov
2017-10-02 12:07 ` Jesper Dangaard Brouer [this message]
2017-10-02 19:44 ` Alexei Starovoitov
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=20171002140723.7667a9b4@redhat.com \
--to=brouer@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andy@greyhouse.net \
--cc=borkmann@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=mchan@broadcom.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peter.waskiewicz.jr@intel.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 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).