From: "luwei (O)" <luwei32@huawei.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"Alexei Starovoitov" <alexei.starovoitov@gmail.com>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
David Ahern <dahern@digitalocean.com>
Subject: Re: Ask for help about bpf map
Date: Tue, 20 Jul 2021 21:05:39 +0800 [thread overview]
Message-ID: <beb37418-4518-100a-5b1b-e036be6f71b6@huawei.com> (raw)
In-Reply-To: <87wnpmtr5j.fsf@toke.dk>
It's very strange, in my virtual host, it is:
$ ip -V
ip utility, iproute2-5.11.0
but in my physical host:
$ ip -V
ip utility, iproute2-5.11.0, libbpf 0.5.0
I compiled iproute2 in the same way as I mentioned previously, and the
kernel versions are both 5.13 (in fact the same code) .
在 2021/7/19 8:38 PM, Toke Høiland-Jørgensen 写道:
> "luwei (O)" <luwei32@huawei.com> writes:
>
>> Andrii and Toke inspired me. You are right, the libbpf version should be included in -V output
>> , but not mine. I searched google and found this page: https://www.spinics.net/lists/netdev/msg700482.html
>> , according which I re-compiled iproute2 and it works.
> Did the libbpf version appear in the output of 'ip -V' after you
> recompiled and enabled it? It does in mine:
>
> $ ./ip/ip -V
> ip utility, iproute2-5.13.0, libbpf 0.4.0
>
> -Toke
>
> .
--
Best Regards,
Lu Wei
next prev parent reply other threads:[~2021-07-20 13:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5aebe6f4-ca0d-4f64-8ee6-b68c58675271@huawei.com>
2021-07-13 16:16 ` Ask for help about bpf map Andrii Nakryiko
2021-07-13 17:07 ` Toke Høiland-Jørgensen
2021-07-14 1:05 ` luwei (O)
2021-07-14 2:02 ` luwei (O)
2021-07-14 8:23 ` luwei (O)
2021-07-14 14:15 ` Toke Høiland-Jørgensen
2021-07-14 14:48 ` Alexei Starovoitov
2021-07-15 1:44 ` luwei (O)
2021-07-19 12:38 ` Toke Høiland-Jørgensen
2021-07-20 13:05 ` luwei (O) [this message]
2021-07-20 14:50 ` Toke Høiland-Jørgensen
2021-07-23 2:07 ` luwei (O)
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=beb37418-4518-100a-5b1b-e036be6f71b6@huawei.com \
--to=luwei32@huawei.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=dahern@digitalocean.com \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.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).