Searched refs:attachments (Results 1 – 14 of 14) sorted by relevance
| /Linux-v5.4/tools/bpf/bpftool/Documentation/ |
| D | bpftool-net.rst | 5 tool for inspection of netdev/tc related bpf prog attachments
34 List bpf program attachments in the kernel networking subsystem.
36 Currently, only device driver xdp attachments and tc filter
37 classification/action attachments are implemented, i.e., for
43 users can use **bpftool cgroup** to dump cgroup attachments.
47 The current output will start with all xdp program attachments, followed by
48 all tc class/qdisc bpf program attachments. Both xdp programs and
|
| D | bpftool-perf.rst | 5 tool for inspection of perf related bpf prog attachments
|
| /Linux-v5.4/Documentation/process/ |
| D | email-clients.rst | 23 attachments, but then the attachments should have content-type
24 ``text/plain``. However, attachments are generally frowned upon because
147 You can safely GPG sign attachments, but inlined text is preferred for
151 If you absolutely must send patches as attachments instead of inlining
261 - Works well for inlining text (or using attachments).
|
| D | 5.Posting.rst | 272 attachments; that makes it much harder for reviewers to quote sections of
|
| D | howto.rst | 419 attachments or compressed patches; they may want to comment on
|
| D | submitting-patches.rst | 340 6) No MIME, no links, no compression, no attachments. Just plain text
|
| /Linux-v5.4/drivers/staging/android/ion/ |
| D | ion.c | 75 INIT_LIST_HEAD(&buffer->attachments); in ion_buffer_create()
202 list_add(&a->list, &buffer->attachments); in ion_dma_buf_attach()
311 list_for_each_entry(a, &buffer->attachments, list) { in ion_dma_buf_begin_cpu_access()
334 list_for_each_entry(a, &buffer->attachments, list) { in ion_dma_buf_end_cpu_access()
|
| D | ion.h | 52 struct list_head attachments; member
|
| /Linux-v5.4/include/linux/ |
| D | dma-buf.h | 299 struct list_head attachments; member
|
| /Linux-v5.4/drivers/dma-buf/ |
| D | dma-buf.c | 338 if (!list_empty(&dmabuf->attachments)) { in dma_buf_set_name()
562 INIT_LIST_HEAD(&dmabuf->attachments); in dma_buf_export()
688 list_add(&attach->node, &dmabuf->attachments); in dma_buf_attach()
1222 list_for_each_entry(attach_obj, &buf_obj->attachments, node) { in dma_buf_debug_show()
|
| /Linux-v5.4/Documentation/devicetree/bindings/ |
| D | xilinx.txt | 146 Also, the system.mhs file defines bus attachments from the processor
148 attachments. Again an example; this system.mhs fragment:
|
| /Linux-v5.4/drivers/misc/ |
| D | fastrpc.c | 125 struct list_head attachments; member
271 INIT_LIST_HEAD(&buf->attachments); in fastrpc_buf_alloc()
539 list_add(&a->node, &buffer->attachments); in fastrpc_dma_buf_attach()
|
| /Linux-v5.4/Documentation/s390/ |
| D | vfio-ccw.rst | 69 different peripheral attachments like disk devices (aka. DASDs), tapes,
|
| D | cds.rst | 118 peripheral attachments like disk devices (aka. DASDs), tapes, communication
|
