From: Thomas Monjalon <thomas@monjalon.net>
To: Gregory Etelson <getelson@nvidia.com>
Cc: andrew.rybchenko@oktetlabs.ru, dev@dpdk.org, mkashani@nvidia.com,
viacheslavo@nvidia.com, matan@nvidia.com,
stephen@networkplumber.org,
David Marchand <david.marchand@redhat.com>
Subject: Re: [RFC PATCH v2] ethdev: support selective Rx data
Date: Tue, 06 Jan 2026 16:04:57 +0100 [thread overview]
Message-ID: <5953641.DvuYhMxLoT@thomas> (raw)
In-Reply-To: <20260105165143.326426-1-getelson@nvidia.com>
05/01/2026 17:51, Gregory Etelson:
> @@ -1757,6 +1761,7 @@ struct rte_eth_rxseg_capa {
> __extension__
> uint32_t multi_pools:1; /**< Supports receiving to multiple pools.*/
> uint32_t offset_allowed:1; /**< Supports buffer offsets. */
> + uint32_t selective_read:1; /**< Supports selective read. */
> uint32_t offset_align_log2:4; /**< Required offset alignment. */
> uint16_t max_nseg; /**< Maximum amount of segments to split. */
> uint16_t reserved; /**< Reserved field. */
Adding a field in the middle in an ABI breakage.
If the ABI checker is smart enough, it should be OK to move the 1-bit field
at the end of the bit-fields.
If we still have an error, we may add an exception to devtools/libabigail.abignore
next prev parent reply other threads:[~2026-01-06 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 13:13 [RFC PATCH] ethdev: support Rx data discard Gregory Etelson
2026-01-04 18:04 ` Stephen Hemminger
2026-01-05 16:51 ` [RFC PATCH v2] ethdev: support selective Rx data Gregory Etelson
2026-01-06 15:04 ` Thomas Monjalon [this message]
2026-01-06 15:45 ` [RFC PATCH v3] " Gregory Etelson
2026-01-06 16:33 ` Stephen Hemminger
2026-01-06 16:52 ` Etelson, Gregory
2026-01-19 1:04 ` fengchengwen
2026-01-19 11:23 ` Etelson, Gregory
2026-01-19 16:37 ` Stephen Hemminger
2026-01-20 17:08 ` Etelson, Gregory
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=5953641.DvuYhMxLoT@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=stephen@networkplumber.org \
--cc=viacheslavo@nvidia.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.