Searched refs:attachments (Results 1 – 19 of 19) sorted by relevance
| /Linux-v5.10/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.10/drivers/dma-buf/heaps/ |
| D | heap-helpers.c | 24 INIT_LIST_HEAD(&buffer->attachments); in init_heap_helper_buffer()
118 list_add(&a->list, &buffer->attachments); in dma_heap_attach()
209 list_for_each_entry(a, &buffer->attachments, list) { in dma_heap_dma_buf_begin_cpu_access()
229 list_for_each_entry(a, &buffer->attachments, list) { in dma_heap_dma_buf_end_cpu_access()
|
| D | heap-helpers.h | 41 struct list_head attachments; member
|
| /Linux-v5.10/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()
300 list_for_each_entry(a, &buffer->attachments, list) in ion_dma_buf_begin_cpu_access()
321 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.10/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
152 You can safely GPG sign attachments, but inlined text is preferred for
156 If you absolutely must send patches as attachments instead of inlining
266 - 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 | 420 attachments or compressed patches; they may want to comment on
|
| D | submitting-patches.rst | 284 No MIME, no links, no compression, no attachments. Just plain text
|
| /Linux-v5.10/drivers/dma-buf/ |
| D | dma-buf.c | 338 if (!list_empty(&dmabuf->attachments)) { in dma_buf_set_name()
570 INIT_LIST_HEAD(&dmabuf->attachments); in dma_buf_export()
706 list_add(&attach->node, &dmabuf->attachments); in dma_buf_dynamic_attach()
961 list_for_each_entry(attach, &dmabuf->attachments, node) in dma_buf_move_notify()
1326 list_for_each_entry(attach_obj, &buf_obj->attachments, node) { in dma_buf_debug_show()
|
| /Linux-v5.10/include/linux/ |
| D | dma-buf.h | 308 struct list_head attachments; member
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | security-bugs.rst | 29 Please send plain text emails without attachments where possible.
31 issue if all the details are hidden away in attachments. Think of it like a
|
| /Linux-v5.10/drivers/misc/ |
| D | fastrpc.c | 150 struct list_head attachments; member
300 INIT_LIST_HEAD(&buf->attachments); in fastrpc_buf_alloc()
570 list_add(&a->node, &buffer->attachments); in fastrpc_dma_buf_attach()
|
| /Linux-v5.10/Documentation/trace/coresight/ |
| D | coresight-ect.rst | 43 no programmed trigger/channel attachments, so will not affect the system
|
| /Linux-v5.10/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
|
| /Linux-v5.10/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_cs.c | 421 list_empty(&bo->tbo.base.dma_buf->attachments))) { in amdgpu_cs_bo_validate()
|
| /Linux-v5.10/Documentation/virt/uml/ |
| D | user_mode_linux_howto_v2.rst | 1079 Note - the list does not accept HTML or attachments, all emails must
|
