From: Zyta Szpak <zr@semihalf.com>
To: Panu Matilainen <pmatilai@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 1/2] ethdev: add callback to get register size in bytes
Date: Tue, 31 May 2016 17:08:39 +0200 [thread overview]
Message-ID: <574DA8F7.7020205@semihalf.com> (raw)
In-Reply-To: <89305686-998b-9f36-d2c2-dc6ec123c5c5@redhat.com>
On 30.05.2016 12:58, Panu Matilainen wrote:
> On 05/30/2016 12:39 PM, zr@semihalf.com wrote:
>> From: Zyta Szpak <zr@semihalf.com>
>>
>> Version 2 of fixing the fixed register width assumption.
>> rte_eth_dev_get_reg_length and rte_eth_dev_get_reg callbacks
>> do not provide register size to the app in any way. It is
>> needed to allocate proper number of bytes before retrieving
>> registers content with rte_eth_dev_get_reg.
>>
>> Signed-off-by: Zyta Szpak <zr@semihalf.com>
> [...]
>> diff --git a/lib/librte_ether/rte_ether_version.map
>> b/lib/librte_ether/rte_ether_version.map
>> index 214ecc7..288bc63 100644
>> --- a/lib/librte_ether/rte_ether_version.map
>> +++ b/lib/librte_ether/rte_ether_version.map
>> @@ -130,5 +130,6 @@ DPDK_16.04 {
>> rte_eth_tx_buffer_drop_callback;
>> rte_eth_tx_buffer_init;
>> rte_eth_tx_buffer_set_err_callback;
>> + rte_eth_dev_get_reg_width;
>>
>> } DPDK_2.2;
>
> This symbol did not exist in DPDK 16.04 so it must not be added there.
> Add a new section for 16.07 which inherits from DPDK_16.04.
>
> - Panu -
>
Right.
next prev parent reply other threads:[~2016-05-31 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 9:39 [PATCH v2 1/2] ethdev: add callback to get register size in bytes zr
2016-05-30 10:58 ` Panu Matilainen
2016-05-31 15:08 ` Zyta Szpak [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-30 9:40 zr
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=574DA8F7.7020205@semihalf.com \
--to=zr@semihalf.com \
--cc=dev@dpdk.org \
--cc=pmatilai@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.