From: Martin KaFai Lau <martin.lau@linux.dev>
To: dongdwdw <dongdwdw@linux.vnet.ibm.com>
Cc: bpf@vger.kernel.org
Subject: Re: Question: any hidden in __sk_buff
Date: Tue, 17 Jan 2023 23:03:38 -0800 [thread overview]
Message-ID: <436be296-16e8-bc8f-bfed-0b2806d0cf49@linux.dev> (raw)
In-Reply-To: <59346030-edd4-30cc-db9e-6fd600713532@linux.vnet.ibm.com>
On 1/17/23 5:26 PM, dongdwdw wrote:
> I am reading ebpf sample code recently. When I read socketx2_kern.c
> socketx2_user.c, I got a question here.
>
> __u64 proto = load_half(skb, 12);
>
>
> I can not understand here: It means load 2 bytes from 12th bytes of skb address
> ( it is a pointer of struct__skb_buff ). >
> struct __sk_buff {
>
> __u32 len;
> __u32 pkt_type;
> __u32 mark;
> __u32 queue_mapping;
> __u32 protocol;
> __u32 vlan_present;
> __u32 vlan_tci;
> __u32 vlan_proto;
>
> ******
>
> }
>
> But I found the structure as above. So the reading start point should be at
> queue_mapping. But it actually reads protocol info here. *And I did found the
> result is protocol info*. Why?
>
> The v*alue of pkt_type, mark, and queue_mapping are all 0.* But when to read
> starting from queue_mapping's offset, the info is about protocol. It is a little
> tricky to me. I can not understand this. From my pointview, the protocol info
> should start at 16 bytes.
>
> Is there any background that is hidden from me? I search a lot and cannot find
> any detailed info about this. Please help explain this. Thanks so much.
If you search for load_half, it is defined in bpf_legacy.h:
/* Functions to emit BPF_LD_ABS and BPF_LD_IND instructions.... */
A search on ABS under Documentation/bpf leads to
Documentation/bpf/instruction-set.rst:
~~~~ snippet ~~~~
BPF_ABS 0x20 legacy BPF packet access (absolute) `Legacy BPF
Packet access instructions`_
BPF_IND 0x40 legacy BPF packet access (indirect) `Legacy BPF
Packet access instructions`_
... ...
Legacy BPF Packet access instructions
-------------------------------------
eBPF previously introduced special instructions for access to packet data that
were carried over from classic BPF. However, these instructions are deprecated
and should no longer be used.
~~~~ snippet ~~~~
Instead of samples/bpf, tools/testing/selftests/bpf/progs is a much better place
to look for examples. eg. The test_tc_*.c that uses skb->protocol.
prev parent reply other threads:[~2023-01-18 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 1:26 Question: any hidden in __sk_buff dongdwdw
2023-01-18 6:24 ` dongdwdw
2023-01-18 7:03 ` Martin KaFai Lau [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=436be296-16e8-bc8f-bfed-0b2806d0cf49@linux.dev \
--to=martin.lau@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=dongdwdw@linux.vnet.ibm.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.