DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Solarflare PMD submission question
Date: Thu, 27 Oct 2016 12:37:58 +0200	[thread overview]
Message-ID: <7987614.kmGMHz0qWb@xps13> (raw)
In-Reply-To: <d0f0fa30-975f-8cce-7074-125f6190e908@solarflare.com>

Hi,

First of all, welcome to DPDK!

2016-10-27 09:34, Andrew Rybchenko:
> Hi,
> 
> we would like to include Solarflare libefx-based PMD in the DPDK 17.02 
> and start the upstreaming process.
> The driver supports Solarflare SFN7xxx and SFN8xxx families of 10/40 
> Gbps adapters.
> The driver has base driver. It is just fresh version of the same code 
> which is used in the FreeBSD [1], illumos [2] and some other Solarflare 
> drivers.

Unfortunately it is common to have some big base drivers in DPDK.
Note that some PMD rely on their kernel counterpart for the control path.
It is a way to avoid code duplication.
As far as I understand, it is easier to share queues with DPDK from kernel
when the device supports an IOMMU.

> The question is how to submit the base driver which is pretty big. Mail 
> size of the patch which imports it is about 2 Mb.

First answer is a question:
Have you thought about cooperating with the kernel driver for your PMD?
If you really cannot use this approach, then we have to maintain this
whole base driver in DPDK.
It will be easier to read, understand and reference if it is a bit split.
Could you try to send it as 10 to 20 patches explaining the role of each
part and giving some design details?

It would be also really appreciated to provide a design documentation
in doc/guides/nics. Are the datasheets open? A link in the doc would help.

> Further changes in the base driver will go in small patches (as it is 
> done, for example, in the FreeBSD).
> The PMD itself is split into small and, I hope, readable and nice patches.

Good to know. Thanks

Please be prepare to work on several iterations of the patch series.

PS: the mailing list put emails exceeding 300KB into a moderation queue.

  reply	other threads:[~2016-10-27 10:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27  6:34 Andrew Rybchenko
2016-10-27 10:37 ` Thomas Monjalon [this message]
2016-10-28 10:50   ` Andrew Rybchenko
2016-10-28 12:33     ` Thomas Monjalon
2016-10-28 13:05       ` Andrew Rybchenko
2016-10-28 13:14         ` Thomas Monjalon
2016-10-28 14:43       ` Andrew Rybchenko
2016-11-18 16:50         ` Andrew Rybchenko
2016-11-21  8:19           ` Thomas Monjalon
2016-11-21  8:46             ` Andrew Rybchenko
2016-11-21  8:59               ` Thomas Monjalon
2016-11-21 10:30                 ` Ferruh Yigit
2016-11-21 15:03                   ` Andrew Rybchenko

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=7987614.kmGMHz0qWb@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    /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).