From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] Solarflare PMD submission question
Date: Fri, 18 Nov 2016 19:50:29 +0300 [thread overview]
Message-ID: <048eabcf-7175-7500-88c4-ffeaa813c4a3@solarflare.com> (raw)
In-Reply-To: <b0978fcf-1bb1-d454-cc72-364c4b7aa9b0@solarflare.com>
On 10/28/2016 05:43 PM, Andrew Rybchenko wrote:
> On 10/28/2016 03:33 PM, Thomas Monjalon wrote:
>> 2016-10-28 13:50, Andrew Rybchenko:
>>> The only thing which comes to my mind is to split libefx import on
>>> subsystem
>>> basis (few files per subsystem). It is artificial and added files will
>>> be abandoned
>>> until the patch which adds them into build. It could be something like:
>>> 1. External interfaces definition
>>> 2. Internal interfaces definition
>>> 3. Registers definition (hardware interface)
>>> 4. Management CPU interface definition (it is one file, but still
>>> big
>>> 650K)
>>> 5. Management CPU interface implementation
>>> and so on for NIC global controls, interrupts, event queue, transmit,
>>> receive,
>>> filtering etc.
>> Yes it is artificial.
>> The most valuable would be a transversal logical split, kind of feature
>> per feature, in order to explain how the device works.
>
> I'm not the main author of the libefx and personally would consider it
> very useful.
> From the other hand I understand that it is a huge amount of work to
> make it.
>
>> Such commit is also the opportunity to explain acronyms and so on.
>
> Good. We'll go this way and 'll do my best to make it useful to
> understand
> overall structure of the code and how the device works.
Now we have a split of the base driver import in big feature steps. The
base driver is split into 28 patches. Just only 1 patch exceeds 300K
boundary (which add MCDI definitions header).
Before submitting 56 patches I'd like to double-check that checkpatch.pl
errors (for example, because of assignments in the 'if' condition,
parenthesis around return value) is not a show-stopper for base driver
import.
Andrew.
next prev parent reply other threads:[~2016-11-18 16:50 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
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 [this message]
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=048eabcf-7175-7500-88c4-ffeaa813c4a3@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).