From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6FF77C3A5A7 for ; Mon, 2 Sep 2019 15:24:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 499AE21883 for ; Mon, 2 Sep 2019 15:24:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731984AbfIBPYC (ORCPT ); Mon, 2 Sep 2019 11:24:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39748 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726394AbfIBPYB (ORCPT ); Mon, 2 Sep 2019 11:24:01 -0400 Received: from mail-qt1-f199.google.com (mail-qt1-f199.google.com [209.85.160.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 1831A3A206 for ; Mon, 2 Sep 2019 15:24:01 +0000 (UTC) Received: by mail-qt1-f199.google.com with SMTP id n59so4450873qtd.8 for ; Mon, 02 Sep 2019 08:24:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=0dOE/s5aGMTaYQho5LnEBg+diYxedKuGjy+hs3paf9w=; b=oyQM+E4HiM98fFf40z1tl7CP1Z6CfcBSPJqXxM/dXHlSpuDA8W1yXT7opKbS0uAy4/ ZRd8D37qfmS++90l0K+2zm/2LWxm63wqzg0rQXsGagqg2bpu77RLirmWI4urrdmRL7N8 hLroiOammciliSjCVTAI50JZy4tRWvvhKhZ8dP5Jtq9Bekxkm6w5mefcynDOLavmViQh t4oLMWkfsvTJAbTh5h/RT8n/QOZykvHN1nRERSSBnGtB92nVKCIjs/SKS6vqKz6gC2B0 oBIjc2k6rf+3N1Xmw8Iozt/IQqdxpFqExiMWZg40fRO/5bQ9RrIVoLPCgn30aMrj50ro OgQg== X-Gm-Message-State: APjAAAXMjrjbFbhvuSWjDYfocuPtVz8GqtHBHayN6Ckg+s/HSlEVR05v 71iIrDV1UsTh8VpaH95LK+DWZgMTuofRXEJD4T4ZfO0lmsdWZ3ICvZ9hgpzqiw6kSQ4miTXK5Qs e7VQkKIgFgbGh X-Received: by 2002:a37:a902:: with SMTP id s2mr7484049qke.239.1567437840442; Mon, 02 Sep 2019 08:24:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqzdrmSh6InBMfIaGf/YSE3mcHFndLjsfUZ2b3BKi/lKrrfRBzrj9Xma+aSpsn1+nw5QdrjzxQ== X-Received: by 2002:a37:a902:: with SMTP id s2mr7484034qke.239.1567437840277; Mon, 02 Sep 2019 08:24:00 -0700 (PDT) Received: from redhat.com (bzq-79-180-62-110.red.bezeqint.net. [79.180.62.110]) by smtp.gmail.com with ESMTPSA id l206sm7034136qke.33.2019.09.02.08.23.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Sep 2019 08:23:59 -0700 (PDT) Date: Mon, 2 Sep 2019 11:23:54 -0400 From: "Michael S. Tsirkin" To: Stefano Garzarella Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Stefan Hajnoczi , "David S. Miller" , virtualization@lists.linux-foundation.org, Jason Wang , kvm@vger.kernel.org Subject: Re: [PATCH v4 1/5] vsock/virtio: limit the memory used per-socket Message-ID: <20190902112317-mutt-send-email-mst@kernel.org> References: <20190729165056.r32uzj6om3o6vfvp@steredhat> <20190729143622-mutt-send-email-mst@kernel.org> <20190730093539.dcksure3vrykir3g@steredhat> <20190730163807-mutt-send-email-mst@kernel.org> <20190801104754.lb3ju5xjfmnxioii@steredhat> <20190801091106-mutt-send-email-mst@kernel.org> <20190801133616.sik5drn6ecesukbb@steredhat> <20190901025815-mutt-send-email-mst@kernel.org> <20190901061707-mutt-send-email-mst@kernel.org> <20190902095723.6vuvp73fdunmiogo@steredhat> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190902095723.6vuvp73fdunmiogo@steredhat> Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Mon, Sep 02, 2019 at 11:57:23AM +0200, Stefano Garzarella wrote: > On Sun, Sep 01, 2019 at 06:17:58AM -0400, Michael S. Tsirkin wrote: > > On Sun, Sep 01, 2019 at 04:26:19AM -0400, Michael S. Tsirkin wrote: > > > On Thu, Aug 01, 2019 at 03:36:16PM +0200, Stefano Garzarella wrote: > > > > On Thu, Aug 01, 2019 at 09:21:15AM -0400, Michael S. Tsirkin wrote: > > > > > On Thu, Aug 01, 2019 at 12:47:54PM +0200, Stefano Garzarella wrote: > > > > > > On Tue, Jul 30, 2019 at 04:42:25PM -0400, Michael S. Tsirkin wrote: > > > > > > > On Tue, Jul 30, 2019 at 11:35:39AM +0200, Stefano Garzarella wrote: > > > > > > > > > > > > (...) > > > > > > > > > > > > > > > > > > > > > > The problem here is the compatibility. Before this series virtio-vsock > > > > > > > > and vhost-vsock modules had the RX buffer size hard-coded > > > > > > > > (VIRTIO_VSOCK_DEFAULT_RX_BUF_SIZE = 4K). So, if we send a buffer smaller > > > > > > > > of 4K, there might be issues. > > > > > > > > > > > > > > Shouldn't be if they are following the spec. If not let's fix > > > > > > > the broken parts. > > > > > > > > > > > > > > > > > > > > > > > Maybe it is the time to add add 'features' to virtio-vsock device. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Stefano > > > > > > > > > > > > > > Why would a remote care about buffer sizes? > > > > > > > > > > > > > > Let's first see what the issues are. If they exist > > > > > > > we can either fix the bugs, or code the bug as a feature in spec. > > > > > > > > > > > > > > > > > > > The vhost_transport '.stream_enqueue' callback > > > > > > [virtio_transport_stream_enqueue()] calls the virtio_transport_send_pkt_info(), > > > > > > passing the user message. This function allocates a new packet, copying > > > > > > the user message, but (before this series) it limits the packet size to > > > > > > the VIRTIO_VSOCK_DEFAULT_RX_BUF_SIZE (4K): > > > > > > > > > > > > static int virtio_transport_send_pkt_info(struct vsock_sock *vsk, > > > > > > struct virtio_vsock_pkt_info *info) > > > > > > { > > > > > > ... > > > > > > /* we can send less than pkt_len bytes */ > > > > > > if (pkt_len > VIRTIO_VSOCK_DEFAULT_RX_BUF_SIZE) > > > > > > pkt_len = VIRTIO_VSOCK_DEFAULT_RX_BUF_SIZE; > > > > > > > > > > > > /* virtio_transport_get_credit might return less than pkt_len credit */ > > > > > > pkt_len = virtio_transport_get_credit(vvs, pkt_len); > > > > > > > > > > > > /* Do not send zero length OP_RW pkt */ > > > > > > if (pkt_len == 0 && info->op == VIRTIO_VSOCK_OP_RW) > > > > > > return pkt_len; > > > > > > ... > > > > > > } > > > > > > > > > > > > then it queues the packet for the TX worker calling .send_pkt() > > > > > > [vhost_transport_send_pkt() in the vhost_transport case] > > > > > > > > > > > > The main function executed by the TX worker is > > > > > > vhost_transport_do_send_pkt() that picks up a buffer from the virtqueue > > > > > > and it tries to copy the packet (up to 4K) on it. If the buffer > > > > > > allocated from the guest will be smaller then 4K, I think here it will > > > > > > be discarded with an error: > > > > > > > > > > > > > > I'm adding more lines to explain better. > > > > > > > > > > static void > > > > > > vhost_transport_do_send_pkt(struct vhost_vsock *vsock, > > > > > > struct vhost_virtqueue *vq) > > > > > > { > > > > ... > > > > > > > > head = vhost_get_vq_desc(vq, vq->iov, ARRAY_SIZE(vq->iov), > > > > &out, &in, NULL, NULL); > > > > > > > > ... > > > > > > > > len = iov_length(&vq->iov[out], in); > > > > iov_iter_init(&iov_iter, READ, &vq->iov[out], in, len); > > > > > > > > nbytes = copy_to_iter(&pkt->hdr, sizeof(pkt->hdr), &iov_iter); > > > > if (nbytes != sizeof(pkt->hdr)) { > > > > virtio_transport_free_pkt(pkt); > > > > vq_err(vq, "Faulted on copying pkt hdr\n"); > > > > break; > > > > } > > > > > > > > > > ... > > > > > > nbytes = copy_to_iter(pkt->buf, pkt->len, &iov_iter); > > > > > > > > > > isn't pck len the actual length though? > > > > > > > > > > > > > It is the length of the packet that we are copying in the guest RX > > > > buffers pointed by the iov_iter. The guest allocates an iovec with 2 > > > > buffers, one for the header and one for the payload (4KB). > > > > > > BTW at the moment that forces another kmalloc within virtio core. Maybe > > > vsock needs a flag to skip allocation in this case. Worth benchmarking. > > > See virtqueue_use_indirect which just does total_sg > 1. > > Okay, I'll take a look at virtqueue_use_indirect and I'll do some > benchmarking. > > > > > > > > > > > > > > if (nbytes != pkt->len) { > > > > > > virtio_transport_free_pkt(pkt); > > > > > > vq_err(vq, "Faulted on copying pkt buf\n"); > > > > > > break; > > > > > > } > > > > > > ... > > > > > > } > > > > > > > > > > > > > > > > > > This series changes this behavior since now we will split the packet in > > > > > > vhost_transport_do_send_pkt() depending on the buffer found in the > > > > > > virtqueue. > > > > > > > > > > > > We didn't change the buffer size in this series, so we still backward > > > > > > compatible, but if we will use buffers smaller than 4K, we should > > > > > > encounter the error described above. > > > > > > So that's an implementation bug then? It made an assumption > > > of a 4K sized buffer? Or even PAGE_SIZE sized buffer? > > Yes, I think it made an assumption and it used this macro as a limit: > > include/linux/virtio_vsock.h:13: > #define VIRTIO_VSOCK_DEFAULT_RX_BUF_SIZE (1024 * 4) > > > > > Assuming we miss nothing and buffers < 4K are broken, > > I think we need to add this to the spec, possibly with > > a feature bit to relax the requirement that all buffers > > are at least 4k in size. > > > > Okay, should I send a proposal to virtio-dev@lists.oasis-open.org? > > Thanks, > Stefano virtio-comment is more appropriate for this. -- MST