DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Huawei Xie <huawei.xie@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 3/3] examples/vhost: add new vhost example
Date: Tue, 5 Aug 2014 20:32:54 -0700	[thread overview]
Message-ID: <20140805203254.2240a09c@haswell.linuxnetplumber.net> (raw)
In-Reply-To: <1407254286-23972-4-git-send-email-huawei.xie@intel.com>


> +static const uint16_t external_pkt_default_vlan_tag = 2000;
> +const uint16_t vlan_tags[] = {
> +	1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007,
> +	1008, 1009, 1010, 1011,	1012, 1013, 1014, 1015,
> +	1016, 1017, 1018, 1019, 1020, 1021, 1022, 1023,
> +	1024, 1025, 1026, 1027, 1028, 1029, 1030, 1031,
> +	1032, 1033, 1034, 1035, 1036, 1037, 1038, 1039,
> +	1040, 1041, 1042, 1043, 1044, 1045, 1046, 1047,
> +	1048, 1049, 1050, 1051, 1052, 1053, 1054, 1055,
> +	1056, 1057, 1058, 1059, 1060, 1061, 1062, 1063,
> +};

Why pre-compute table if it is just: vlan_tag = n + 1000?


> +
> +/* Per-device statistics struct */
> +struct device_statistics {
> +	uint64_t tx_total;
> +	rte_atomic64_t rx_total_atomic;
> +	uint64_t rx_total;
> +	uint64_t tx;
> +	rte_atomic64_t rx_atomic;
> +	uint64_t rx;
> +} __rte_cache_aligned;
> +struct device_statistics dev_statistics[MAX_DEVICES];

Doing per-core statistics would be faster than using atomic's
which have implicit lock.

> +/*
> + * Builds up the correct configuration for VMDQ VLAN pool map
> + * according to the pool & queue limits.
> + */
> +static inline int
> +get_eth_conf(struct rte_eth_conf *eth_conf, uint32_t num_devices)
> +{
> +	struct rte_eth_vmdq_rx_conf conf;
> +	unsigned i;
> +
> +	memset(&conf, 0, sizeof(conf));
> +	conf.nb_queue_pools = (enum rte_eth_nb_pools)num_devices;
> +	conf.nb_pool_maps = num_devices;
> +	conf.enable_loop_back =
> +		vmdq_conf_default.rx_adv_conf.vmdq_rx_conf.enable_loop_back;
> +
> +	for (i = 0; i < conf.nb_pool_maps; i++) {
> +		conf.pool_map[i].vlan_id = vlan_tags[i];
> +		conf.pool_map[i].pools = (1UL << i);
> +	}
> +
> +	(void)(rte_memcpy(eth_conf, &vmdq_conf_default, sizeof(*eth_conf)));
> +	(void)(rte_memcpy(&eth_conf->rx_adv_conf.vmdq_rx_conf, &conf,
> +		   sizeof(eth_conf->rx_adv_conf.vmdq_rx_conf)));
> +	return 0;
> +}

If function always returns 0 just make it void.
No point in making non-fastpath code inline.
The cast to (void) is unnecessary and just makes things ugly.
Why not use structure assignment rather than memcpy() which is not type safe?

  reply	other threads:[~2014-08-06  3:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 15:58 [dpdk-dev] [PATCH 0/3] vhost example based on user space vhost library Huawei Xie
2014-08-05 15:58 ` [dpdk-dev] [PATCH 1/3] examples/vhost: remove old vhost example Huawei Xie
2014-08-05 15:58 ` [dpdk-dev] [PATCH 2/3] lib/librte_vhost: add lib/librte_vhost support in mk/rte.app.mk Huawei Xie
2014-08-05 15:58 ` [dpdk-dev] [PATCH 3/3] examples/vhost: add new vhost example Huawei Xie
2014-08-06  3:32   ` Stephen Hemminger [this message]
2014-08-06  5:34     ` Xie, Huawei
2014-08-06  3:09 ` [dpdk-dev] [PATCH 0/3] vhost example based on user space vhost library Fu, JingguoX
2014-08-07 14:29 ` Cao, Waterman
2014-08-19  8:50   ` Tahhan, Maryam
2014-08-19  9:06     ` Xie, Huawei
2014-08-19 12:35       ` Tahhan, Maryam

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=20140805203254.2240a09c@haswell.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=huawei.xie@intel.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 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).