DPDK usage discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ran Shalit <ranshalit@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] dpdk - for video frames too ?
Date: Thu, 12 Nov 2015 09:49:39 +0100	[thread overview]
Message-ID: <1990785.CcVbSUjEhi@xps13> (raw)
In-Reply-To: <CAJ2oMhLgbebhcn+Z8tYOtCuqdVtfpsGpPMtnFsgBcQg+Ko4eew@mail.gmail.com>

2015-11-12 09:14, Ran Shalit:
> I need to develop a driver/application which capture and output video
> frames from PCIe device , and is using Intel cpu (i7), Centand Intel's
> media sdk server framework for the video compression.
> 
> I am not sure what will be a better choice between the following 2 options:
> 1. application which use dpdk for capture and output to the PCIe device
> 2. v4l driver for the PCIe device
> 
> dpdk is supposed to be able to read/write from PCIe device too.
> I tried to see the prons/cons of dpdk compared to v4l.
> 
> prons of dpdk, as I understand them:
> 1. userspace application (easier debugging compared to kernel
> debugging of v4l device driver)
> 2. supposed better performance
> 
> cons of dpdk compared to v4l:
> 1. I could not find examples for PCIe device usage , or samples for
> showing how application (such as media sdk) use dpdk video frames.

There is no API for video currently.
There is an API for networking drivers and a crypto API is coming.
If you feel a DPDK poll mode driver would be a good design, you are
welcome to do it. In case it brings some performance improvement,
it can be decided (no guarantee) to integrate it in the scope of the DPDK.

  reply	other threads:[~2015-11-12  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12  7:14 Ran Shalit
2015-11-12  8:49 ` Thomas Monjalon [this message]
2015-12-04 16:30   ` Ran Shalit
2015-12-04 17:13     ` Thomas Monjalon

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=1990785.CcVbSUjEhi@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=ranshalit@gmail.com \
    --cc=users@dpdk.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).