Nick Allen created METRON-1024:
----------------------------------
Summary: Fastcapa - Configure NIC Interface Dynamically
Key: METRON-1024
URL: https://issues.apache.org/jira/browse/METRON-1024
Project: Metron
Issue Type: Improvement
Affects Versions: 0.4.0
Reporter: Nick Allen
This JIRA fell out of a conversation in
https://github.com/apache/metron/pull/608.
h5. [~cestella] asks:
Just curious for the uninitiated, if I'm running a non-X520 but another DPDK
supported card, is that supported via configuration changes only or do those
require code changes at this point?
h5. [~nickwallen] answers:
What we have should work out-of-the-box for most NICs. Of course, I
have only been able to test on the x520 and Cisco VNICs, so that is all I can
really be sure of.
If changes would be needed for another NIC, it would likely be in the
initialization of the rte_eth_conf and rte_eth_txconf structs. The defaults are
currently provided in nic.c.
I was going to make this configurable, but decided not to in this PR
due to the amount of work needed. I would have had to define configurable
values that populate all of the possible fields in each of these structs (which
are quite numerous). I would have had to allow configuration of these values
via the config file, rather than just the command-line, since they are so
numerous.
There is also the challenge of how to allow a user to dynamically
configure values that are effectively macros, if that is even possible. For
example, how should a user define something like the following in a
configuration file? I'd have to dig for a good way to handle this.
{code}
static const struct rte_eth_conf rx_conf_default = {
.rxmode = {
.mq_mode = ETH_MQ_RX_RSS,
...
}
}
{code}
h5. [~cestella] responds:
That sounds good; can you create a follow-on JIRA to investigate how to make
the properties specified at run-time rather than as macros in code?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
