From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Andrew Rybchenko <arybchenko@solarflare.com>, DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] I/O device memory read/write implementation for sfc
Date: Thu, 19 Jan 2017 11:23:41 +0530 [thread overview]
Message-ID: <20170119055340.GA26867@localhost.localdomain> (raw)
In-Reply-To: <d5ce4fdf-003d-0dd9-c1f2-2ad577ba8552@intel.com>
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
next prev parent reply other threads:[~2017-01-19 5:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 19:31 Ferruh Yigit
2017-01-19 5:53 ` Jerin Jacob [this message]
2017-01-19 6:30 ` Andrew Rybchenko
2017-01-19 12:48 ` Ferruh Yigit
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=20170119055340.GA26867@localhost.localdomain \
--to=jerin.jacob@caviumnetworks.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/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).