From: Jakub Kicinski <kuba@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: luigi.leonardi@outlook.com, mst@redhat.com,
Stefan Hajnoczi <stefanha@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
kvm@vger.kernel.org, virtualization@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Marco Pinna <marco.pinn95@gmail.com>
Subject: Re: [PATCH net-next v4 0/2] vsock: avoid queuing on intermediate queue if possible
Date: Tue, 6 Aug 2024 09:02:57 -0700 [thread overview]
Message-ID: <20240806090257.48724974@kernel.org> (raw)
In-Reply-To: <tblrar34qivcwsvai7z5fepxhi4irknbyne5xqqoqowwf3nwt5@kyd2nmqghews>
On Mon, 5 Aug 2024 10:39:23 +0200 Stefano Garzarella wrote:
> this series is marked as "Not Applicable" for the net-next tree:
> https://patchwork.kernel.org/project/netdevbpf/patch/20240730-pinna-v4-2-5c9179164db5@outlook.com/
>
> Actually this is more about the virtio-vsock driver, so can you queue
> this on your tree?
We can revive it in our patchwork, too, if that's easier.
Not entirely sure why it was discarded, seems borderline.
next prev parent reply other threads:[~2024-08-06 16:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 19:47 [PATCH net-next v4 0/2] vsock: avoid queuing on intermediate queue if possible Luigi Leonardi
2024-07-30 19:47 ` Luigi Leonardi via B4 Relay
2024-07-30 19:47 ` [PATCH net-next v4 1/2] vsock/virtio: refactor virtio_transport_send_pkt_work Luigi Leonardi
2024-07-30 19:47 ` Luigi Leonardi via B4 Relay
2024-07-30 19:47 ` [PATCH net-next v4 2/2] vsock/virtio: avoid queuing packets when intermediate queue is empty Luigi Leonardi
2024-07-30 19:47 ` Luigi Leonardi via B4 Relay
2024-07-31 7:39 ` Stefano Garzarella
2024-08-05 8:39 ` [PATCH net-next v4 0/2] vsock: avoid queuing on intermediate queue if possible Stefano Garzarella
2024-08-06 16:02 ` Jakub Kicinski [this message]
2024-08-06 16:45 ` Stefano Garzarella
2024-08-29 11:00 ` Luigi Leonardi
2024-08-29 12:19 ` Michael S. Tsirkin
2024-08-29 12:33 ` Stefano Garzarella
2024-08-29 12:37 ` Michael S. Tsirkin
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=20240806090257.48724974@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luigi.leonardi@outlook.com \
--cc=marco.pinn95@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
/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.