From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47]) by dpdk.org (Postfix) with ESMTP id 00FA4919D for ; Thu, 12 Nov 2015 09:50:51 +0100 (CET) Received: by wmdw130 with SMTP id w130so144432787wmd.0 for ; Thu, 12 Nov 2015 00:50:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind_com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:organization:user-agent :in-reply-to:references:mime-version:content-transfer-encoding :content-type; bh=/8vvr85gJq8tSnaNnlnUEO4Vnob1R+GoBoOd7px86Cs=; b=R2DmOenKduW+7ssmlpaxba5UK26SXqCvlgLGpX9SAApvZspIWVHgaOq1cAmj2i6vil U4DkDwOyZt3KGjoKBCB4XjQfxvpvhGwzccHwKjuBPoJflrPvGKGGSfwXOmhzjM35PWWQ C3HyirU2aHzuHHvcalf9mF9T1a9DcHqWDG3KYOf87rOJMRK8YLRkAfULvxCn7GbxdpeG LEU9/gcyNU+SOYQ/6GeEmQDwwBtpa/siUjr8X1Jzd9TVFpA2OLPBz87MiOxSPSBt93c6 MtOSLNplco+vcQXa53SIoKWANDmOZ65AXbXeu+bK4PTccyujhg0j66Y1P55ZKOmGn5tQ ETEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=/8vvr85gJq8tSnaNnlnUEO4Vnob1R+GoBoOd7px86Cs=; b=YPrRrF3U6vsnCgHuoJaeLkjy+wFGONAmhbfErUmUYC+m4vaVpw71leEHjURF1FLZgC m2QIXBd/foSZP5iUjhmFHhTsej1eLHf4LCrDAF1rbbhQuxQoiL+h7z5QghjhdeEQRn9I QCR5Yseqph4ID1k6E80UTLmZ2++eIkBKOzMPPhd6nyHr05oSEEZoyge/TUyfTAJ2HOw+ VxOIiTX4P9of6OvNAJ7E91pkmXA78vaUcGx82I+M2PZj6hT88qkpTpbVjetdYeppI0Y6 qYJJf03n6+mkEAAmTmu9d8S4IZgX7KXfK6XN0l/bRLD3r+gYMisuyvzmSVwC+4ag9QeA mLfw== X-Gm-Message-State: ALoCoQmDFz93eSv8+4CCSzTtrN689HIFJ97+kArbwwzgXFm4tVGdmF2mYFUVbktMC5pYQ7lOl/OI X-Received: by 10.28.35.203 with SMTP id j194mr11391699wmj.13.1447318251707; Thu, 12 Nov 2015 00:50:51 -0800 (PST) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id 71sm13804801wmm.24.2015.11.12.00.50.50 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Nov 2015 00:50:50 -0800 (PST) From: Thomas Monjalon To: Ran Shalit Date: Thu, 12 Nov 2015 09:49:39 +0100 Message-ID: <1990785.CcVbSUjEhi@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: users@dpdk.org Subject: Re: [dpdk-users] dpdk - for video frames too ? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2015 08:50:52 -0000 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.