From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Rybchenko Subject: Re: I/O device memory read/write implementation for sfc Date: Thu, 19 Jan 2017 09:30:08 +0300 Message-ID: <9707c383-7621-e4e2-3427-ce0bf57e52b2@solarflare.com> References: <20170119055340.GA26867@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Cc: Andrew Rybchenko , DPDK To: Jerin Jacob , Ferruh Yigit Return-path: Received: from nbfkord-smmo01.seg.att.com (nbfkord-smmo01.seg.att.com [209.65.160.76]) by dpdk.org (Postfix) with ESMTP id 6CD8FFB4F for ; Thu, 19 Jan 2017 07:30:21 +0100 (CET) In-Reply-To: <20170119055340.GA26867@localhost.localdomain> 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 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. Thanks, Andrew.