From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
linux-media@vger.kernel.org, jani.nikula@linux.intel.com,
anisse@astier.eu, Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Ricardo Ribalda <ribalda@chromium.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] media: Virtual camera driver
Date: Sun, 01 Feb 2026 21:26:24 +0100 [thread overview]
Message-ID: <5073898.31r3eYUQgx@natalenko.name> (raw)
In-Reply-To: <20260201212133.1849a49e@foz.lan>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
On neděle 1. února 2026 21:21:33, středoevropský standardní čas Mauro Carvalho Chehab wrote:
> > My use-case for v4l2loopback is to stream a webcam from one machine to another (with the help of ffmpeg). Is this covered by something other than v4l2loopback now?
>
> Using a kernel driver for something like that is a bad idea and may end
> causing dead lock problems. You may also have performance issues and
> high network traffic. The best solution for it is to use a proper
> userspace tool, like obs:
>
> https://obsproject.com/kb/linux-installation
Ignoring the fact I've never had any performance issues, and I don't care much about how big the traffic is in my isolated VLAN dedicated to this specific task, the OBS solution still uses v4l2loopback under the hood. Could you please tell me what do I miss in this regard?
Thank you.
--
Oleksandr Natalenko, MSE
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-01 20:26 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 13:33 Jarkko Sakkinen
2026-02-01 18:20 ` Laurent Pinchart
2026-02-01 19:04 ` Jarkko Sakkinen
2026-02-01 20:06 ` Laurent Pinchart
2026-02-01 20:14 ` Oleksandr Natalenko
2026-02-01 20:21 ` Mauro Carvalho Chehab
2026-02-01 20:26 ` Oleksandr Natalenko [this message]
2026-02-01 23:17 ` Mauro Carvalho Chehab
2026-02-01 23:17 ` Mauro Carvalho Chehab
2026-02-01 23:25 ` Oleksandr Natalenko
2026-02-02 1:02 ` Mauro Carvalho Chehab
2026-02-02 7:16 ` Oleksandr Natalenko
2026-02-02 11:41 ` Laurent Pinchart
2026-02-02 9:05 ` Jarkko Sakkinen
2026-02-02 9:19 ` Jarkko Sakkinen
2026-02-02 11:43 ` Laurent Pinchart
2026-02-02 11:36 ` Gergo Koteles
2026-02-02 11:40 ` Laurent Pinchart
2026-02-02 11:45 ` Oleksandr Natalenko
2026-02-03 1:23 ` Laurent Pinchart
2026-02-03 14:38 ` Oleksandr Natalenko
2026-02-03 14:53 ` Laurent Pinchart
2026-02-03 20:36 ` Laurent Pinchart
2026-02-03 21:39 ` Oleksandr Natalenko
2026-02-03 21:49 ` Laurent Pinchart
2026-02-03 20:49 ` Laurent Pinchart
2026-04-06 12:23 ` Oleksandr Natalenko
2026-04-06 12:37 ` Laurent Pinchart
2026-02-01 20:22 ` Laurent Pinchart
2026-02-01 20:27 ` Oleksandr Natalenko
2026-02-01 20:41 ` Laurent Pinchart
2026-02-01 20:35 ` Jarkko Sakkinen
2026-02-01 20:54 ` Jarkko Sakkinen
2026-02-01 21:09 ` Laurent Pinchart
2026-02-02 1:44 ` Jarkko Sakkinen
2026-02-01 21:01 ` Laurent Pinchart
2026-02-01 22:03 ` Jarkko Sakkinen
2026-02-03 9:50 ` Jani Nikula
2026-02-03 15:06 ` Laurent Pinchart
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=5073898.31r3eYUQgx@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=anisse@astier.eu \
--cc=hverkuil@kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=jani.nikula@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome