From: Tom Rix <trix@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>,
dev@dpdk.org, gakhil@marvell.com, nipun.gupta@nxp.com
Cc: thomas@monjalon.net, mingshan.zhang@intel.com,
arun.joshi@intel.com, hemant.agrawal@nxp.com,
david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH v9] bbdev: add device info related to data endianness assumption
Date: Thu, 7 Oct 2021 05:01:04 -0700 [thread overview]
Message-ID: <e38faad4-3144-39a7-a6a0-0190984ba3cf@redhat.com> (raw)
In-Reply-To: <1633553929-58670-2-git-send-email-nicolas.chautru@intel.com>
On 10/6/21 1:58 PM, Nicolas Chautru wrote:
> Adding device information to capture explicitly the assumption
> of the input/output data byte endianness being processed.
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
> doc/guides/rel_notes/release_21_11.rst | 1 +
> drivers/baseband/acc100/rte_acc100_pmd.c | 1 +
> drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c | 1 +
> drivers/baseband/fpga_lte_fec/fpga_lte_fec.c | 1 +
Missed bbdev_null.c
If this was intentional data_endianness is uninitialized or implicitly
big endian.
It would be better to say it is unknown. which may mean another enum is
needed.
> drivers/baseband/turbo_sw/bbdev_turbo_software.c | 1 +
> lib/bbdev/rte_bbdev.h | 8 ++++++++
> 6 files changed, 13 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_21_11.rst b/doc/guides/rel_notes/release_21_11.rst
> index a8900a3..f0b3006 100644
> --- a/doc/guides/rel_notes/release_21_11.rst
> +++ b/doc/guides/rel_notes/release_21_11.rst
> @@ -191,6 +191,7 @@ API Changes
>
> * bbdev: Added capability related to more comprehensive CRC options.
>
> +* bbdev: Added device info related to data byte endianness processing assumption.
>
> ABI Changes
> -----------
> diff --git a/drivers/baseband/acc100/rte_acc100_pmd.c b/drivers/baseband/acc100/rte_acc100_pmd.c
> index 4e2feef..eb2c6c1 100644
> --- a/drivers/baseband/acc100/rte_acc100_pmd.c
> +++ b/drivers/baseband/acc100/rte_acc100_pmd.c
> @@ -1089,6 +1089,7 @@
> #else
> dev_info->harq_buffer_size = 0;
> #endif
> + dev_info->data_endianness = RTE_BBDEV_LITTLE_ENDIAN;
> acc100_check_ir(d);
> }
>
> diff --git a/drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c b/drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c
> index 6485cc8..c7f15c0 100644
> --- a/drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c
> +++ b/drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c
> @@ -372,6 +372,7 @@
> dev_info->default_queue_conf = default_queue_conf;
> dev_info->capabilities = bbdev_capabilities;
> dev_info->cpu_flag_reqs = NULL;
> + dev_info->data_endianness = RTE_BBDEV_LITTLE_ENDIAN;
>
> /* Calculates number of queues assigned to device */
> dev_info->max_num_queues = 0;
> diff --git a/drivers/baseband/fpga_lte_fec/fpga_lte_fec.c b/drivers/baseband/fpga_lte_fec/fpga_lte_fec.c
> index 350c424..72e213e 100644
> --- a/drivers/baseband/fpga_lte_fec/fpga_lte_fec.c
> +++ b/drivers/baseband/fpga_lte_fec/fpga_lte_fec.c
> @@ -644,6 +644,7 @@ struct __rte_cache_aligned fpga_queue {
> dev_info->default_queue_conf = default_queue_conf;
> dev_info->capabilities = bbdev_capabilities;
> dev_info->cpu_flag_reqs = NULL;
> + dev_info->data_endianness = RTE_BBDEV_LITTLE_ENDIAN;
>
> /* Calculates number of queues assigned to device */
> dev_info->max_num_queues = 0;
> diff --git a/drivers/baseband/turbo_sw/bbdev_turbo_software.c b/drivers/baseband/turbo_sw/bbdev_turbo_software.c
> index e1db2bf..0cab91a 100644
> --- a/drivers/baseband/turbo_sw/bbdev_turbo_software.c
> +++ b/drivers/baseband/turbo_sw/bbdev_turbo_software.c
> @@ -253,6 +253,7 @@ struct turbo_sw_queue {
> dev_info->capabilities = bbdev_capabilities;
> dev_info->min_alignment = 64;
> dev_info->harq_buffer_size = 0;
> + dev_info->data_endianness = RTE_BBDEV_LITTLE_ENDIAN;
>
> rte_bbdev_log_debug("got device info from %u\n", dev->data->dev_id);
> }
> diff --git a/lib/bbdev/rte_bbdev.h b/lib/bbdev/rte_bbdev.h
> index 3ebf62e..b3f3000 100644
> --- a/lib/bbdev/rte_bbdev.h
> +++ b/lib/bbdev/rte_bbdev.h
> @@ -49,6 +49,12 @@ enum rte_bbdev_state {
> RTE_BBDEV_INITIALIZED
> };
>
> +/** Definitions of device data byte endianness types */
> +enum rte_bbdev_endianness {
> + RTE_BBDEV_BIG_ENDIAN, /**< Data with byte-endianness BE */
> + RTE_BBDEV_LITTLE_ENDIAN, /**< Data with byte-endianness LE */
> +};
Could RTE_BIG|LITTLE_ENDIAN be reused ?
Tom
> +
> /**
> * Get the total number of devices that have been successfully initialised.
> *
> @@ -309,6 +315,8 @@ struct rte_bbdev_driver_info {
> uint16_t min_alignment;
> /** HARQ memory available in kB */
> uint32_t harq_buffer_size;
> + /** Byte endianness assumption for input/output data */
> + enum rte_bbdev_endianness data_endianness;
> /** Default queue configuration used if none is supplied */
> struct rte_bbdev_queue_conf default_queue_conf;
> /** Device operation capabilities */
next prev parent reply other threads:[~2021-10-07 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 20:58 Nicolas Chautru
2021-10-06 20:58 ` Nicolas Chautru
2021-10-07 12:01 ` Tom Rix [this message]
2021-10-07 15:19 ` Chautru, Nicolas
2021-10-07 13:13 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-07 15:41 ` Chautru, Nicolas
2021-10-07 16:49 ` Nipun Gupta
2021-10-07 18:58 ` Chautru, Nicolas
2021-10-08 4:34 ` Nipun Gupta
2021-10-07 2:22 ` [dpdk-dev] " Nipun Gupta
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=e38faad4-3144-39a7-a6a0-0190984ba3cf@redhat.com \
--to=trix@redhat.com \
--cc=arun.joshi@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=mingshan.zhang@intel.com \
--cc=nicolas.chautru@intel.com \
--cc=nipun.gupta@nxp.com \
--cc=thomas@monjalon.net \
/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).