From: Matej Vido <vido@cesnet.cz>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "Jan Remeš" <remes@netcope.com>,
dev@dpdk.org, fpga-sw <fpga-sw@netcope.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/3] net/szedata2: add support for new NIC
Date: Wed, 18 Apr 2018 09:21:09 +0200 [thread overview]
Message-ID: <90271791-d96b-b756-f5c3-90e1136a88b8@cesnet.cz> (raw)
In-Reply-To: <169d539d-a30c-dd80-394c-7740aac9c0de@intel.com>
On 13.04.2018 18:29, Ferruh Yigit wrote:
> On 4/13/2018 4:03 PM, Jan Remeš wrote:
>> It is mentioned on the website with the packages itself. The current
>> version works with the reworked PMD - there is a headline which says:
>> "DPDK from 18.05" (since we expect the patches to land in the upcoming
>> release; we will update it if this does not happen).
>>
>> The older version is still available on the website, with appropriate
>> installation steps and a headline that says "DPDK up to 18.02".
>>
>> Is this form of documentation sufficient for you or would you like to
>> see it mentioned in the DPDK documentation as well?
> I think it is better to have some level of information in DPDK documentation too.
>
> There is already a release note update in this set, do you think does it make
> sense to mention new dependency there?
>
> I will get patches right now, please send doc/release notes updates as
> incremental patches.
Hi Ferruh,
we will send the follow-up patches updating both documentation and
release notes soon.
Thanks,
Matej
>
>> Thanks,
>> Jan
>> Jan Remeš | Software Developer
>> Netcope Technologies, a.s.
>>
>> T: +420 530 510 680
>> A: Sochorova 3232/34, Brno, 616 00, Czech Republic
>> W: www.netcope.com
>>
>>
>>
>>
>> On Fri, Apr 13, 2018 at 4:26 PM, Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>>> On 4/13/2018 9:17 AM, Jan Remeš wrote:
>>>>> Hi Matej,
>>>>>
>>>>> Where szedata_get_area_numa_node() is defined?
>>>>> Is it possible that you are missing a patch?
>>>>>
>>>>> Thanks,
>>>>> ferruh
>>>> Hi Ferruh,
>>>>
>>>> the new PMD requires an updated version of libsze2 and drivers. We
>>>> have just published the updated packages here:
>>>> https://www.netcope.com/en/company/community-support/dpdk-libsze2.
>>> DPDK documentation mentions about libsze2 dependency but there is no version
>>> mentioned.
>>>
>>> And I have not seen any note that says a new version of library is required,
>>> perhaps I missed it, is there a documentation which says which version of DPDK
>>> requires which version of the dependencies?
>>>
>>> What is the way of tracing this dependency?
>>>
>>>> Sorry for the hickup.
>>>>
>>>> Best regards,
>>>> Jan
>>>>
next prev parent reply other threads:[~2018-04-18 7:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 14:12 [dpdk-dev] [PATCH 0/3] net/szedata2: patch set for new card support Matej Vido
2018-04-06 14:12 ` [dpdk-dev] [PATCH 1/3] net/szedata2: do not affect Ethernet interfaces Matej Vido
2018-04-10 15:28 ` Ferruh Yigit
2018-04-11 9:36 ` Matej Vido
2018-04-11 10:51 ` Ferruh Yigit
2018-04-12 7:38 ` Matej Vido
2018-04-13 4:25 ` Yasufumi Ogawa
2018-04-13 10:39 ` Matej Vido
2018-04-06 14:12 ` [dpdk-dev] [PATCH 2/3] net/szedata2: add support for new NIC Matej Vido
2018-04-06 14:12 ` [dpdk-dev] [PATCH 3/3] net/szedata2: add kernel module dependency Matej Vido
2018-04-12 7:41 ` [dpdk-dev] [PATCH v2 0/3] net/szedata2: patch set for new card support Matej Vido
2018-04-13 16:32 ` Ferruh Yigit
2018-04-27 8:57 ` [dpdk-dev] [PATCH 1/1] doc: update doc and release notes for szedata2 driver Matej Vido
2018-04-27 13:11 ` Ferruh Yigit
2018-04-12 7:41 ` [dpdk-dev] [PATCH v2 1/3] net/szedata2: do not affect Ethernet interfaces Matej Vido
2018-04-12 7:41 ` [dpdk-dev] [PATCH v2 2/3] net/szedata2: add support for new NIC Matej Vido
2018-04-12 16:11 ` Ferruh Yigit
2018-04-13 8:17 ` Jan Remeš
2018-04-13 14:26 ` Ferruh Yigit
2018-04-13 15:03 ` Jan Remeš
2018-04-13 16:29 ` Ferruh Yigit
2018-04-18 7:21 ` Matej Vido [this message]
2018-04-12 7:41 ` [dpdk-dev] [PATCH v2 3/3] net/szedata2: add kernel module dependency Matej Vido
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=90271791-d96b-b756-f5c3-90e1136a88b8@cesnet.cz \
--to=vido@cesnet.cz \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fpga-sw@netcope.com \
--cc=remes@netcope.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).