From: David Miller <davem@davemloft.net>
To: maowenan@huawei.com
Cc: netdev@vger.kernel.org, jeffrey.t.kirsher@intel.com,
alexander.duyck@gmail.com
Subject: Re: [PATCH v2 net-next] net:add one common config ARCH_WANT_RELAX_ORDER to support relax ordering.
Date: Tue, 17 Jan 2017 14:15:33 -0500 (EST) [thread overview]
Message-ID: <20170117.141533.680344033700095483.davem@davemloft.net> (raw)
In-Reply-To: <1483939954-9864-1-git-send-email-maowenan@huawei.com>
From: Mao Wenan <maowenan@huawei.com>
Date: Mon, 9 Jan 2017 13:32:34 +0800
> Relax ordering(RO) is one feature of 82599 NIC, to enable this feature can
> enhance the performance for some cpu architecure, such as SPARC and so on.
> Currently it only supports one special cpu architecture(SPARC) in 82599
> driver to enable RO feature, this is not very common for other cpu architecture
> which really needs RO feature.
> This patch add one common config CONFIG_ARCH_WANT_RELAX_ORDER to set RO feature,
> and should define CONFIG_ARCH_WANT_RELAX_ORDER in sparc Kconfig firstly.
>
> Signed-off-by: Mao Wenan <maowenan@huawei.com>
Since no-one has reviewed this patch, and I do not feel comfortable with applying
it without such review, I am tossing this patch.
If someone eventually reviews it, repost this patch.
next prev parent reply other threads:[~2017-01-17 19:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 5:32 [PATCH v2 net-next] net:add one common config ARCH_WANT_RELAX_ORDER to support relax ordering Mao Wenan
2017-01-09 12:07 ` maowenan
2017-01-16 4:40 ` David Miller
2017-01-17 19:15 ` David Miller [this message]
2017-01-17 19:27 ` Alexander Duyck
2017-01-18 1:07 ` maowenan
2017-01-18 16:22 ` David Laight
2017-01-18 17:25 ` Alexander Duyck
2017-01-19 11:43 ` David Laight
2017-01-19 15:54 ` Alexander Duyck
2017-01-23 9:44 ` David Laight
2017-01-23 16:28 ` Alexander Duyck
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=20170117.141533.680344033700095483.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.duyck@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=maowenan@huawei.com \
--cc=netdev@vger.kernel.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).