From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerin Jacob Subject: Re: I/O device memory read/write implementation for sfc Date: Thu, 19 Jan 2017 11:23:41 +0530 Message-ID: <20170119055340.GA26867@localhost.localdomain> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Andrew Rybchenko , DPDK To: Ferruh Yigit Return-path: Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0042.outbound.protection.outlook.com [104.47.36.42]) by dpdk.org (Postfix) with ESMTP id 9BA7CFB4E for ; Thu, 19 Jan 2017 06:54:05 +0100 (CET) Content-Disposition: inline In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, Jan 18, 2017 at 07:31:39PM +0000, Ferruh Yigit wrote: > Hi Andrew, Jerin, > > Existing "I/O device memory read/write" doesn't cover sfc driver because > driver was in next-net tree. > > And both sfc and "I/O device memory read/write" patches will be > integrated into main tree for rc1 release. > > If "I/O device memory read/write" implementation can be done for sfc > before rc2, that changes can be merged into rc2 release. > > Who can work on this task? sfc driver does not even support non x86 build for now. I can spend some time if Andrew's does not have any bandwidth to work on this task. > > Thanks, > ferruh