From: Bagas Sanjaya <bagasdotme@gmail•com>
To: Mina Almasry <almasrymina@google•com>,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-doc@vger•kernel.org, virtualization@lists•linux.dev,
kvm@vger•kernel.org, linux-kselftest@vger•kernel.org
Cc: "David S. Miller" <davem@davemloft•net>,
"Eric Dumazet" <edumazet@google•com>,
"Jakub Kicinski" <kuba@kernel•org>,
"Paolo Abeni" <pabeni@redhat•com>,
"Simon Horman" <horms@kernel•org>,
"Donald Hunter" <donald.hunter@gmail•com>,
"Jonathan Corbet" <corbet@lwn•net>,
"Andrew Lunn" <andrew+netdev@lunn•ch>,
"Jeroen de Borst" <jeroendb@google•com>,
"Praveen Kaligineedi" <pkaligineedi@google•com>,
"Shailend Chand" <shailend@google•com>,
"Kuniyuki Iwashima" <kuniyu@amazon•com>,
"Willem de Bruijn" <willemb@google•com>,
"David Ahern" <dsahern@kernel•org>,
"Neal Cardwell" <ncardwell@google•com>,
"Michael S. Tsirkin" <mst@redhat•com>,
"Jason Wang" <jasowang@redhat•com>,
"Xuan Zhuo" <xuanzhuo@linux•alibaba.com>,
"Eugenio Pérez" <eperezma@redhat•com>,
"Stefan Hajnoczi" <stefanha@redhat•com>,
"Stefano Garzarella" <sgarzare@redhat•com>,
"Shuah Khan" <shuah@kernel•org>,
sdf@fomichev•me, asml.silence@gmail•com, dw@davidwei•uk,
"Jamal Hadi Salim" <jhs@mojatatu•com>,
"Victor Nogueira" <victor@mojatatu•com>,
"Pedro Tammela" <pctammela@mojatatu•com>,
"Samiullah Khawaja" <skhawaja@google•com>
Subject: Re: [PATCH net-next v4 5/9] net: add devmem TCP TX documentation
Date: Thu, 20 Feb 2025 15:13:35 +0700 [thread overview]
Message-ID: <Z7bkL7uuy8prxfTe@archie.me> (raw)
In-Reply-To: <20250220020914.895431-6-almasrymina@google.com>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On Thu, Feb 20, 2025 at 02:09:10AM +0000, Mina Almasry wrote:
> +The user application must use MSG_ZEROCOPY flag when sending devmem TCP. Devmem
> +cannot be copied by the kernel, so the semantics of the devmem TX are similar
> +to the semantics of MSG_ZEROCOPY.
> +
> + setsockopt(socket_fd, SOL_SOCKET, SO_ZEROCOPY, &opt, sizeof(opt));
> +
> +It is also recommended that the user binds the TX socket to the same interface
> +the dma-buf has been bound to via SO_BINDTODEVICE.
> +
> + setsockopt(socket_fd, SOL_SOCKET, SO_BINDTODEVICE, ifname, strlen(ifname) + 1);
> +
Wrap both setsockopts above in literal code-block (just like other snippets
for consistency).
> +The user should create a msghdr where,
> +
> +iov_base is set to the offset into the dmabuf to start sending from.
> +iov_len is set to the number of bytes to be sent from the dmabuf.
Should above be bullet list?
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-02-20 8:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 2:09 [PATCH net-next v4 0/9] Device memory TCP TX Mina Almasry
2025-02-20 2:09 ` [PATCH net-next v4 1/9] net: add get_netmem/put_netmem support Mina Almasry
2025-02-20 19:34 ` Stanislav Fomichev
2025-02-20 2:09 ` [PATCH net-next v4 2/9] net: devmem: TCP tx netlink api Mina Almasry
2025-02-20 2:09 ` [PATCH net-next v4 3/9] net: devmem: Implement TX path Mina Almasry
2025-02-20 21:00 ` Stanislav Fomichev
2025-02-20 2:09 ` [PATCH net-next v4 4/9] net: devmem: make dmabuf unbinding scheduled work Mina Almasry
2025-02-20 21:00 ` Stanislav Fomichev
2025-02-20 2:09 ` [PATCH net-next v4 5/9] net: add devmem TCP TX documentation Mina Almasry
2025-02-20 8:13 ` Bagas Sanjaya [this message]
2025-02-20 21:04 ` Stanislav Fomichev
2025-02-20 2:09 ` [PATCH net-next v4 6/9] net: enable driver support for netmem TX Mina Almasry
2025-02-20 19:13 ` Stanislav Fomichev
2025-02-22 0:11 ` Mina Almasry
2025-02-22 0:35 ` Stanislav Fomichev
2025-02-20 2:09 ` [PATCH net-next v4 7/9] gve: add netmem TX support to GVE DQO-RDA mode Mina Almasry
2025-02-20 2:09 ` [PATCH net-next v4 8/9] net: check for driver support in netmem TX Mina Almasry
2025-02-20 21:05 ` Stanislav Fomichev
2025-02-20 2:09 ` [PATCH net-next v4 9/9] selftests: ncdevmem: Implement devmem TCP TX Mina Almasry
2025-02-20 19:09 ` Stanislav Fomichev
2025-02-20 20:01 ` Stanislav Fomichev
2025-02-22 0:08 ` Mina Almasry
2025-02-22 0:20 ` Stanislav Fomichev
2025-02-22 0:24 ` Mina Almasry
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=Z7bkL7uuy8prxfTe@archie.me \
--to=bagasdotme@gmail$(echo .)com \
--cc=almasrymina@google$(echo .)com \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=asml.silence@gmail$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=donald.hunter@gmail$(echo .)com \
--cc=dsahern@kernel$(echo .)org \
--cc=dw@davidwei$(echo .)uk \
--cc=edumazet@google$(echo .)com \
--cc=eperezma@redhat$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jasowang@redhat$(echo .)com \
--cc=jeroendb@google$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kuniyu@amazon$(echo .)com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=mst@redhat$(echo .)com \
--cc=ncardwell@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pctammela@mojatatu$(echo .)com \
--cc=pkaligineedi@google$(echo .)com \
--cc=sdf@fomichev$(echo .)me \
--cc=sgarzare@redhat$(echo .)com \
--cc=shailend@google$(echo .)com \
--cc=shuah@kernel$(echo .)org \
--cc=skhawaja@google$(echo .)com \
--cc=stefanha@redhat$(echo .)com \
--cc=victor@mojatatu$(echo .)com \
--cc=virtualization@lists$(echo .)linux.dev \
--cc=willemb@google$(echo .)com \
--cc=xuanzhuo@linux$(echo .)alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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