From: Jakub Kicinski <kuba@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: namespaced vsock
Date: Wed, 5 Jun 2024 14:22:52 -0700 [thread overview]
Message-ID: <20240605142252.466c3af4@kernel.org> (raw)
In-Reply-To: <myowlo6xpjrhbawt6sptwcqktm34zbfnsxzyo5eahcbspitwzq@ypssm5pe6q7m>
On Wed, 5 Jun 2024 18:00:25 +0200 Stefano Garzarella wrote:
> On Wed, Jun 05, 2024 at 07:57:44AM GMT, Jakub Kicinski wrote:
>> I found you patches from 2020 adding netns support to vsock.
>> I got an internal ping from someone trying to run VMMs inside
>> containers. Any plans on pushing that work forward? Is there
>> a reason you stopped, or just EBUSY?
>
> IIRC nothing too difficult to solve, but as you guessed more EBUSY ;-)
>
> Maybe the more laborious one is somehow exporting a netdev interface
> into the guest to assign the device to a netns. But I hadn't tried to
> see if that was feasible yet. I have some notes here:
> https://gitlab.com/vsock/vsock/-/issues/2
>
> I've been planning to take it up several times but haven't found time
> for now, if there's anyone interested I'm happy to share information and
> help with review and feedback. Otherwise I try to allocate some time,
> but I can't promise anything in the short term.
Makes sense, thanks for the info!
> Do you have time or anyone interested in continuing the work?
Depending on the priority compared to other work, as usual :(
There was a small chance you'd say "I'm planning to do it next month"
and I wouldn't have to worry at all, so I thought I'd ask ;)
next prev parent reply other threads:[~2024-06-05 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 14:57 namespaced vsock Jakub Kicinski
2024-06-05 16:00 ` Stefano Garzarella
2024-06-05 21:22 ` Jakub Kicinski [this message]
2024-06-06 14:05 ` Stefano Garzarella
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=20240605142252.466c3af4@kernel.org \
--to=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
/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.