All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
To: Stefan Hajnoczi <stefanha@redhat.com>,
	Stefano Garzarella <sgarzare@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Bobby Eshleman <bobby.eshleman@bytedance.com>
Cc: <kvm@vger.kernel.org>,
	<virtualization@lists.linux-foundation.org>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<kernel@sberdevices.ru>, <oxffffaa@gmail.com>,
	<avkrasnov@sberdevices.ru>,
	Arseniy Krasnov <AVKrasnov@sberdevices.ru>
Subject: [RFC PATCH v3 01/17] vsock/virtio: read data from non-linear skb
Date: Mon, 22 May 2023 10:39:34 +0300	[thread overview]
Message-ID: <20230522073950.3574171-2-AVKrasnov@sberdevices.ru> (raw)
In-Reply-To: <20230522073950.3574171-1-AVKrasnov@sberdevices.ru>

This is preparation patch for non-linear skbuff handling. It replaces
direct calls of 'memcpy_to_msg()' with 'skb_copy_datagram_iter()'. Main
advantage of the second one is that is can handle paged part of the skb
by using 'kmap()' on each page, but if there are no pages in the skb,
it behaves like simple copying to iov iterator. This patch also removes
'skb_pull()' calls, because it updates 'data' pointer of the skb (it is
wrong thing to do with non-linear skb). Instead of updating 'data' and
'len' fields of skb, it adds new field to the control block of the skb:
this value shows current offset to read next data from skb (no matter
that this skb is linear or not), after each read from skb this field is
incremented and once it reaches 'len', skb is considered done.

Signed-off-by: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
---
 include/linux/virtio_vsock.h            |  1 +
 net/vmw_vsock/virtio_transport_common.c | 26 +++++++++++++++++--------
 2 files changed, 19 insertions(+), 8 deletions(-)

diff --git a/include/linux/virtio_vsock.h b/include/linux/virtio_vsock.h
index c58453699ee9..17dbb7176e37 100644
--- a/include/linux/virtio_vsock.h
+++ b/include/linux/virtio_vsock.h
@@ -12,6 +12,7 @@
 struct virtio_vsock_skb_cb {
 	bool reply;
 	bool tap_delivered;
+	u32 frag_off;
 };
 
 #define VIRTIO_VSOCK_SKB_CB(skb) ((struct virtio_vsock_skb_cb *)((skb)->cb))
diff --git a/net/vmw_vsock/virtio_transport_common.c b/net/vmw_vsock/virtio_transport_common.c
index e4878551f140..16effa8d55d2 100644
--- a/net/vmw_vsock/virtio_transport_common.c
+++ b/net/vmw_vsock/virtio_transport_common.c
@@ -355,7 +355,7 @@ virtio_transport_stream_do_peek(struct vsock_sock *vsk,
 	spin_lock_bh(&vvs->rx_lock);
 
 	skb_queue_walk_safe(&vvs->rx_queue, skb,  tmp) {
-		off = 0;
+		off = VIRTIO_VSOCK_SKB_CB(skb)->frag_off;
 
 		if (total == len)
 			break;
@@ -370,7 +370,10 @@ virtio_transport_stream_do_peek(struct vsock_sock *vsk,
 			 */
 			spin_unlock_bh(&vvs->rx_lock);
 
-			err = memcpy_to_msg(msg, skb->data + off, bytes);
+			err = skb_copy_datagram_iter(skb, off,
+						     &msg->msg_iter,
+						     bytes);
+
 			if (err)
 				goto out;
 
@@ -414,24 +417,28 @@ virtio_transport_stream_do_dequeue(struct vsock_sock *vsk,
 		skb = skb_peek(&vvs->rx_queue);
 
 		bytes = len - total;
-		if (bytes > skb->len)
-			bytes = skb->len;
+		if (bytes > skb->len - VIRTIO_VSOCK_SKB_CB(skb)->frag_off)
+			bytes = skb->len - VIRTIO_VSOCK_SKB_CB(skb)->frag_off;
 
 		/* sk_lock is held by caller so no one else can dequeue.
 		 * Unlock rx_lock since memcpy_to_msg() may sleep.
 		 */
 		spin_unlock_bh(&vvs->rx_lock);
 
-		err = memcpy_to_msg(msg, skb->data, bytes);
+		err = skb_copy_datagram_iter(skb,
+					     VIRTIO_VSOCK_SKB_CB(skb)->frag_off,
+					     &msg->msg_iter, bytes);
+
 		if (err)
 			goto out;
 
 		spin_lock_bh(&vvs->rx_lock);
 
 		total += bytes;
-		skb_pull(skb, bytes);
 
-		if (skb->len == 0) {
+		VIRTIO_VSOCK_SKB_CB(skb)->frag_off += bytes;
+
+		if (skb->len == VIRTIO_VSOCK_SKB_CB(skb)->frag_off) {
 			u32 pkt_len = le32_to_cpu(virtio_vsock_hdr(skb)->len);
 
 			virtio_transport_dec_rx_pkt(vvs, pkt_len);
@@ -503,7 +510,10 @@ static int virtio_transport_seqpacket_do_dequeue(struct vsock_sock *vsk,
 				 */
 				spin_unlock_bh(&vvs->rx_lock);
 
-				err = memcpy_to_msg(msg, skb->data, bytes_to_copy);
+				err = skb_copy_datagram_iter(skb, 0,
+							     &msg->msg_iter,
+							     bytes_to_copy);
+
 				if (err) {
 					/* Copy of message failed. Rest of
 					 * fragments will be freed without copy.
-- 
2.25.1


  reply	other threads:[~2023-05-22  7:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22  7:39 [RFC PATCH v3 00/17] vsock: MSG_ZEROCOPY flag support Arseniy Krasnov
2023-05-22  7:39 ` Arseniy Krasnov [this message]
2023-05-22  7:39 ` [RFC PATCH v3 02/17] vhost/vsock: read data from non-linear skb Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 03/17] vsock/virtio: support to send " Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 04/17] vsock/virtio: non-linear skb handling for tap Arseniy Krasnov
2023-05-22 13:13   ` Simon Horman
2023-05-22 13:15     ` Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 05/17] vsock/virtio: MSG_ZEROCOPY flag support Arseniy Krasnov
2023-05-22 13:11   ` Simon Horman
2023-05-22 13:09     ` Arseniy Krasnov
2023-05-23  5:46       ` Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 06/17] vsock: check error queue to set EPOLLERR Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 07/17] vsock: read from socket's error queue Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 08/17] vsock: check for MSG_ZEROCOPY support Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 09/17] vsock: enable SOCK_SUPPORT_ZC bit Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 10/17] vhost/vsock: support MSG_ZEROCOPY for transport Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 11/17] vsock/virtio: " Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 12/17] vsock/loopback: " Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 13/17] net/sock: enable setting SO_ZEROCOPY for PF_VSOCK Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 14/17] docs: net: description of MSG_ZEROCOPY for AF_VSOCK Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 15/17] test/vsock: MSG_ZEROCOPY flag tests Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 16/17] test/vsock: MSG_ZEROCOPY support for vsock_perf Arseniy Krasnov
2023-05-22  7:39 ` [RFC PATCH v3 17/17] test/vsock: io_uring rx/tx tests Arseniy Krasnov
2023-05-25 15:56 ` [RFC PATCH v3 00/17] vsock: MSG_ZEROCOPY flag support Arseniy Krasnov
2023-05-26 10:30   ` Stefano Garzarella
2023-05-26 10:30     ` Stefano Garzarella
2023-05-26 11:36     ` Arseniy Krasnov
2023-05-26 12:23       ` Stefano Garzarella
2023-05-26 12:23         ` Stefano Garzarella
2023-05-26 12:28         ` Arseniy Krasnov

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=20230522073950.3574171-2-AVKrasnov@sberdevices.ru \
    --to=avkrasnov@sberdevices.ru \
    --cc=bobby.eshleman@bytedance.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jasowang@redhat.com \
    --cc=kernel@sberdevices.ru \
    --cc=kuba@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=oxffffaa@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux-foundation.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.