From: Zhe Tao <zhe.tao@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] i40e & ixgbe xmit issue: txe->next_id
Date: Fri, 4 Mar 2016 03:17:48 +0800 [thread overview]
Message-ID: <20160303191032.GA9550@intel.com> (raw)
Hi all,
I have a question about why we need the txe->next_id field in the i40e&ixgbe Tx
function?
>From the current implementation, all the txe is initialized and free sequentially,
so we don't need this "next_id" field in our TX function, and when we decide the
"last_id" for txe, we assume the txe is sequential. So I suggest deprecate using
this next_id field.
Any comments will be welcome!
reply other threads:[~2016-03-04 3:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160303191032.GA9550@intel.com \
--to=zhe.tao@intel.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).