From: Stephen Hemminger <stephen@networkplumber.org>
To: nickcooper-zhangtonghao <nic@opencloud.tech>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 1/5] eal: Set numa node value for system which not support NUMA.
Date: Thu, 5 Jan 2017 08:17:14 -0800 [thread overview]
Message-ID: <20170105081714.44b74f91@xeon-e3> (raw)
In-Reply-To: <1483617709-7088-1-git-send-email-nic@opencloud.tech>
On Thu, 5 Jan 2017 04:01:45 -0800
nickcooper-zhangtonghao <nic@opencloud.tech> wrote:
> The NUMA node information for PCI devices provided through
> sysfs is invalid for AMD Opteron(TM) Processor 62xx and 63xx
> on Red Hat Enterprise Linux 6, and VMs on some hypervisors.
>
> Signed-off-by: nickcooper-zhangtonghao <nic@opencloud.tech>
That name seems a bit unusual. Is that your legal name or a partnership?
The Signed-off-by line has legal significance and it is important that
you use your legal name. Please use the name you would use when
signing a legal document (like buying a house or renting).
next prev parent reply other threads:[~2017-01-05 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 12:01 [PATCH v2 1/5] eal: Set numa node value for system which not support NUMA nickcooper-zhangtonghao
2017-01-05 12:01 ` [PATCH v2 2/5] vmxnet3: Avoid memory leak in vmxnet3_dev_rx_queue_setup nickcooper-zhangtonghao
2017-01-05 12:01 ` [PATCH v2 3/5] vmxnet3: Avoid segfault caused by vmxnet3_dev_rx_queue_setup nickcooper-zhangtonghao
2017-01-05 12:01 ` [PATCH v2 4/5] vmxnet3: Avoid memory leak in vmxnet3_dev_tx_queue_setup nickcooper-zhangtonghao
2017-01-05 12:01 ` [PATCH v2 5/5] vmxnet3: Avoid segfault caused by vmxnet3_dev_tx_queue_setup nickcooper-zhangtonghao
2017-01-05 14:23 ` [PATCH v2 1/5] eal: Set numa node value for system which not support NUMA Ferruh Yigit
2017-01-06 0:01 ` Yong Wang
2017-01-09 2:06 ` nickcooper-zhangtonghao
2017-01-09 2:20 ` nickcooper-zhangtonghao
2017-01-05 16:17 ` Stephen Hemminger [this message]
2017-01-05 16:26 ` Stephen Hemminger
2017-01-09 2:14 ` nickcooper-zhangtonghao
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=20170105081714.44b74f91@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=nic@opencloud.tech \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.