From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Paolo Abeni" <pabeni@redhat.com>,
kvm@vger.kernel.org, netdev@vger.kernel.org,
"Bobby Eshleman" <bobby.eshleman@gmail.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
"Eric Dumazet" <edumazet@google.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
davem@davemloft.net, "Junichi Uekawa ( 上川純一)" <uekawa@google.com>
Subject: Re: [PATCH] vhost/vsock: Use kvmalloc/kvfree for larger packets.
Date: Thu, 29 Sep 2022 12:25:14 -0400 [thread overview]
Message-ID: <20220929122444-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220929090731.27cda58c@kernel.org>
On Thu, Sep 29, 2022 at 09:07:31AM -0700, Jakub Kicinski wrote:
> On Thu, 29 Sep 2022 03:49:18 -0400 Michael S. Tsirkin wrote:
> > net tree would be preferable, my pull for this release is kind of ready ... kuba?
>
> If we're talking about 6.1 - we can take it, no problem.
I think they want it in 6.0 as it fixes a crash.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2022-09-29 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220928064538.667678-1-uekawa@chromium.org>
2022-09-28 8:28 ` [PATCH] vhost/vsock: Use kvmalloc/kvfree for larger packets Stefano Garzarella
2022-09-28 9:31 ` Michael S. Tsirkin
2022-09-28 15:11 ` Stefano Garzarella
2022-09-28 20:02 ` Michael S. Tsirkin
2022-09-29 7:40 ` Stefano Garzarella
2022-09-29 7:47 ` Michael S. Tsirkin
[not found] ` <CADgJSGHxPWXJjbakEeWnqF42A03yK7Dpw6U1SKNLhk+B248Ymg@mail.gmail.com>
2022-09-29 7:19 ` Michael S. Tsirkin
2022-09-29 7:46 ` Stefano Garzarella
2022-09-29 7:49 ` Michael S. Tsirkin
[not found] ` <20220929090731.27cda58c@kernel.org>
2022-09-29 16:25 ` 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=20220929122444-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=bobby.eshleman@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefanha@redhat.com \
--cc=uekawa@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).