From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?SnVuaWNoaSBVZWthd2EgKOS4iuW3nee0lOS4gCkgPHVla2F3YUBjaHJvbWl1bS5v?=@ci.codeaurora.org,
=?utf-8?b?cmc+?=@ci.codeaurora.org
Cc: stefanha@redhat.com, sgarzare@redhat.com, jasowang@redhat.com,
edumazet@google.com, davem@davemloft.net, netdev@vger.kernel.org,
kuba@kernel.org, virtualization@lists.linux-foundation.org,
kvm@vger.kernel.org, mst@redhat.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vhost/vsock: Use kvmalloc/kvfree for larger packets.
Date: Fri, 30 Sep 2022 01:50:14 +0000 [thread overview]
Message-ID: <166450261468.15562.8337973902056212950.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220928064538.667678-1-uekawa@chromium.org>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 28 Sep 2022 15:45:38 +0900 you wrote:
> When copying a large file over sftp over vsock, data size is usually 32kB,
> and kmalloc seems to fail to try to allocate 32 32kB regions.
>
> Call Trace:
> [<ffffffffb6a0df64>] dump_stack+0x97/0xdb
> [<ffffffffb68d6aed>] warn_alloc_failed+0x10f/0x138
> [<ffffffffb68d868a>] ? __alloc_pages_direct_compact+0x38/0xc8
> [<ffffffffb664619f>] __alloc_pages_nodemask+0x84c/0x90d
> [<ffffffffb6646e56>] alloc_kmem_pages+0x17/0x19
> [<ffffffffb6653a26>] kmalloc_order_trace+0x2b/0xdb
> [<ffffffffb66682f3>] __kmalloc+0x177/0x1f7
> [<ffffffffb66e0d94>] ? copy_from_iter+0x8d/0x31d
> [<ffffffffc0689ab7>] vhost_vsock_handle_tx_kick+0x1fa/0x301 [vhost_vsock]
> [<ffffffffc06828d9>] vhost_worker+0xf7/0x157 [vhost]
> [<ffffffffb683ddce>] kthread+0xfd/0x105
> [<ffffffffc06827e2>] ? vhost_dev_set_owner+0x22e/0x22e [vhost]
> [<ffffffffb683dcd1>] ? flush_kthread_worker+0xf3/0xf3
> [<ffffffffb6eb332e>] ret_from_fork+0x4e/0x80
> [<ffffffffb683dcd1>] ? flush_kthread_worker+0xf3/0xf3
>
> [...]
Here is the summary with links:
- vhost/vsock: Use kvmalloc/kvfree for larger packets.
https://git.kernel.org/netdev/net/c/0e3f72931fc4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-09-30 1:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 6:45 [PATCH] vhost/vsock: Use kvmalloc/kvfree for larger packets Junichi Uekawa
2022-09-28 8:28 ` Stefano Garzarella
2022-09-28 9:31 ` Michael S. Tsirkin
2022-09-28 15:11 ` Stefano Garzarella
2022-09-27 10:36 ` Bobby Eshleman
2022-09-28 20:02 ` Michael S. Tsirkin
2022-09-29 7:40 ` Stefano Garzarella
2022-09-29 7:47 ` Michael S. Tsirkin
2022-09-28 23:14 ` Junichi Uekawa (上川純一)
2022-09-29 7:19 ` Michael S. Tsirkin
2022-09-29 7:46 ` Stefano Garzarella
2022-09-29 7:49 ` Michael S. Tsirkin
2022-09-29 16:07 ` Jakub Kicinski
2022-09-29 16:25 ` Michael S. Tsirkin
2022-09-29 18:07 ` Jakub Kicinski
2022-09-30 0:49 ` Junichi Uekawa (上川純一)
2022-09-30 1:35 ` Jakub Kicinski
2022-09-30 1:50 ` patchwork-bot+netdevbpf [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=166450261468.15562.8337973902056212950.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?SnVuaWNoaSBVZWthd2EgKOS4iuW3nee0lOS4gCkgPHVla2F3YUBjaHJvbWl1bS5v?=@ci.codeaurora.org \
--cc==?utf-8?b?cmc+?=@ci.codeaurora.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--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=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 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).