From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: I/O device memory read/write implementation for sfc Date: Thu, 19 Jan 2017 12:48:53 +0000 Message-ID: References: <20170119055340.GA26867@localhost.localdomain> <9707c383-7621-e4e2-3427-ce0bf57e52b2@solarflare.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: DPDK To: Andrew Rybchenko , Jerin Jacob Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 451515A44 for ; Thu, 19 Jan 2017 13:48:55 +0100 (CET) In-Reply-To: <9707c383-7621-e4e2-3427-ce0bf57e52b2@solarflare.com> 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 1/19/2017 6:30 AM, Andrew Rybchenko wrote: > On 01/19/2017 08:53 AM, Jerin Jacob wrote: >> 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. > > Don't worry. I'll do. Thank you Andrew. > > Thanks, > Andrew.