From: "Michael S. Tsirkin" <mst@redhat.com>
To: bjorn.topel@intel.com
Cc: netdev@vger.kernel.org
Subject: af_xdp zero copy ideas
Date: Wed, 14 Nov 2018 03:10:04 -0500 [thread overview]
Message-ID: <20181114025153-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20180604120601.18123-1-bjorn.topel@gmail.com>
So a I mentioned during the presentation for the af_xdp zero copy I
think it's pretty important to be able to close the device and get back
the affected memory. One way would be to unmap the DMA memory from
userspace and map in some other memory. It's tricky since you need
to also replace the mapping to the backing file which could be
hugetlbfs, tmpfs, just a file ...
HTH,
--
MST
prev parent reply other threads:[~2018-11-14 18:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 12:05 [Intel-wired-lan] [PATCH bpf-next 00/11] AF_XDP: introducing zero-copy support =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:05 ` Björn Töpel
2018-06-04 12:05 ` [Intel-wired-lan] [PATCH bpf-next 01/11] xsk: moved struct xdp_umem definition =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:05 ` Björn Töpel
2018-06-04 12:05 ` [Intel-wired-lan] [PATCH bpf-next 02/11] xsk: introduce xdp_umem_page =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:05 ` Björn Töpel
2019-03-13 9:39 ` [Intel-wired-lan] [bpf-next, " Jiri Slaby
2019-03-13 9:39 ` [bpf-next,02/11] " Jiri Slaby
2019-03-13 11:23 ` [Intel-wired-lan] [bpf-next, 02/11] " =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2019-03-13 11:23 ` [bpf-next,02/11] " Björn Töpel
2018-06-04 12:05 ` [Intel-wired-lan] [PATCH bpf-next 03/11] net: xdp: added bpf_netdev_command XDP_{QUERY, SETUP}_XSK_UMEM =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:05 ` [PATCH bpf-next 03/11] net: xdp: added bpf_netdev_command XDP_{QUERY,SETUP}_XSK_UMEM Björn Töpel
2018-06-04 12:05 ` [Intel-wired-lan] [PATCH bpf-next 04/11] xdp: add MEM_TYPE_ZERO_COPY =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:05 ` Björn Töpel
2018-06-04 12:05 ` [Intel-wired-lan] [PATCH bpf-next 05/11] xsk: add zero-copy support for Rx =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:05 ` Björn Töpel
2018-06-04 12:05 ` [Intel-wired-lan] [PATCH bpf-next 06/11] net: added netdevice operation for Tx =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:05 ` Björn Töpel
2018-06-04 12:05 ` [Intel-wired-lan] [PATCH bpf-next 07/11] xsk: wire upp Tx zero-copy functions =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:05 ` Björn Töpel
2018-06-04 12:05 ` [Intel-wired-lan] [PATCH bpf-next 08/11] i40e: added queue pair disable/enable functions =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:05 ` Björn Töpel
2018-06-04 12:05 ` [Intel-wired-lan] [PATCH bpf-next 09/11] i40e: implement AF_XDP zero-copy support for Rx =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:05 ` Björn Töpel
2018-06-04 20:35 ` [Intel-wired-lan] " Alexander Duyck
2018-06-04 20:35 ` Alexander Duyck
2018-06-07 7:40 ` [Intel-wired-lan] " =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-07 7:40 ` Björn Töpel
2018-06-04 12:06 ` [Intel-wired-lan] [PATCH bpf-next 10/11] i40e: implement AF_XDP zero-copy support for Tx =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:06 ` Björn Töpel
2018-06-04 20:53 ` [Intel-wired-lan] " Alexander Duyck
2018-06-04 20:53 ` Alexander Duyck
2018-06-05 12:43 ` [Intel-wired-lan] " Jesper Dangaard Brouer
2018-06-05 12:43 ` Jesper Dangaard Brouer
2018-06-05 13:07 ` [Intel-wired-lan] " =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-05 13:07 ` Björn Töpel
2018-06-04 12:06 ` [Intel-wired-lan] [PATCH bpf-next 11/11] samples/bpf: xdpsock: use skb Tx path for XDP_SKB =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2018-06-04 12:06 ` Björn Töpel
2018-06-04 16:38 ` [Intel-wired-lan] [PATCH bpf-next 00/11] AF_XDP: introducing zero-copy support Alexei Starovoitov
2018-06-04 16:38 ` Alexei Starovoitov
2018-06-04 20:29 ` [Intel-wired-lan] " Jeff Kirsher
2018-06-04 20:29 ` Jeff Kirsher
2018-11-14 8:10 ` Michael S. Tsirkin [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=20181114025153-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=bjorn.topel@intel.com \
--cc=netdev@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.