From: Sowmini Varadhan <sowmini05@gmail.com>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: "xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Toke Høiland-Jørgensen" <toke@redhat.com>
Subject: Re: building eBPF
Date: Mon, 27 Apr 2020 06:49:38 -0400 [thread overview]
Message-ID: <20200427104938.GF488@gmail.com> (raw)
In-Reply-To: <20200427120333.7e6cedfc@carbon>
> The iproute2 BPF-loader does not support BTF. I think upstream agrees
> that it would be too much work to add (and maintain) it, so the current
> plan[1] is to convert iproute2 to use libbpf instead.
So I updated my iproute2 because I was initially getting an error like
" Error fixing up map structure, incompatible struct bpf_elf_map used?
Error fetching ELF ancillary data!
Unable to load program
"
with the native iproute2 binaries, and thought it may be due to
a header mismatch.
> Why do you want to use 'tc' to load XDP?
I was merely using the exsiting example in samples to try to understand
this. If the existing example is misleading, it should be removed.
> I actually think this is only a warning, and the program is actually
> loaded...
no I dont believe it is. if you insert a break in the script before
it gets to cleanup, and try
# ip netns exec ns2 bash
# tc filter show dev vens2
it will not show any loaded filters.
--Sowmini
next prev parent reply other threads:[~2020-04-27 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200425122225.GA455@gmail.com>
2020-04-25 12:56 ` building eBPF Jesper Dangaard Brouer
2020-04-25 16:16 ` David Ahern
2020-04-25 16:34 ` Sowmini Varadhan
2020-04-27 10:46 ` Toke Høiland-Jørgensen
2020-04-27 0:20 ` Sowmini Varadhan
2020-04-27 10:03 ` Jesper Dangaard Brouer
2020-04-27 10:49 ` Sowmini Varadhan [this message]
2020-04-27 12:08 ` Daniel Borkmann
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=20200427104938.GF488@gmail.com \
--to=sowmini05@gmail.com \
--cc=brouer@redhat.com \
--cc=stephen@networkplumber.org \
--cc=toke@redhat.com \
--cc=xdp-newbies@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 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.