> -Original Message-
> From: Stephen Hemminger [mailto:step...@networkplumber.org]
>
> PCI table should be const
Ok. Will do.
> -Original Message-
> From: Stephen Hemminger [mailto:step...@networkplumber.org]
>
> What exactly is the spinlock protecting? The control operations in DPDK are
> defined to be not thread safe. I.e it is responsibility of caller to
> synchronize.
> Therefore is lock really needed?
The
On Sun, 26 Feb 2017 14:08:55 -0500
Allain Legacy wrote:
> +struct avp_dev {
> + uint32_t magic; /**< Memory validation marker */
> + uint64_t device_id; /**< Unique system identifier */
> + struct ether_addr ethaddr; /**< Host specified MAC address */
> + struct rte_eth_dev_data *
On Sun, 26 Feb 2017 14:08:55 -0500
Allain Legacy wrote:
> +static struct rte_pci_id pci_id_avp_map[] = {
> + { .vendor_id = RTE_AVP_PCI_VENDOR_ID,
> + .device_id = RTE_AVP_PCI_DEVICE_ID,
> + .subsystem_vendor_id = RTE_AVP_PCI_SUB_VENDOR_ID,
> + .subsystem_device_id = RTE_AVP
Adds the initial framework for registering the driver against the support
PCI device identifiers.
Signed-off-by: Allain Legacy
Signed-off-by: Matt Peters
---
config/common_linuxapp | 1 +
config/defconfig_i686-native-linuxapp-gcc| 5 +
config/defconfig_i686-native-
5 matches
Mail list logo
