From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] API feature check _HAS_
Date: Thu, 26 Nov 2015 21:35:03 +0100 [thread overview]
Message-ID: <13076727.eWbPQotoSK@xps13> (raw)
When introducing LRO, Vlad has defined the macro RTE_ETHDEV_HAS_LRO_SUPPORT:
http://dpdk.org/browse/dpdk/commit/lib/librte_ether/rte_ethdev.h?id=8eecb329
It allows to use the feature without version check (before the release or
after a backport).
Do you think it is useful?
Should we define other macros RTE_[API]_HAS_[FEATURE] for each new feature
or API change?
It's time to fix it before releasing the 2.2 version.
next reply other threads:[~2015-11-26 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 20:35 Thomas Monjalon [this message]
2015-11-29 9:07 ` Vlad Zolotarov
2015-11-29 9:10 ` Gleb Natapov
2015-11-29 9:43 ` Vlad Zolotarov
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=13076727.eWbPQotoSK@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
/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).