From: Ding Tianhong <dingtianhong@huawei.com>
To: David Miller <davem@davemloft.net>
Cc: <jeffrey.t.kirsher@intel.com>, <keescook@chromium.org>,
<linux-kernel@vger.kernel.org>, <sparclinux@vger.kernel.org>,
<intel-wired-lan@lists.osuosl.org>, <alexander.duyck@gmail.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH net 0/2] net: ixgbe: Use new flag to disable Relaxed Ordering
Date: Thu, 17 Aug 2017 09:22:46 +0800 [thread overview]
Message-ID: <ea51f2cc-49f7-3689-d503-23c56e6fe90b@huawei.com> (raw)
In-Reply-To: <20170816.105647.341781221143669151.davem@davemloft.net>
On 2017/8/17 1:56, David Miller wrote:
> From: Ding Tianhong <dingtianhong@huawei.com>
> Date: Wed, 16 Aug 2017 17:41:45 +0800
>
>> The new flag PCI_DEV_FLAGS_NO_RELAXED_ORDERING has been added
>> to indicate that Relaxed Ordering Attributes (RO) should not
>> be used for Transaction Layer Packets (TLP) targeted toward
>> these affected Root Port, it will clear the bit4 in the PCIe
>> Device Control register, so the PCIe device drivers could
>> query PCIe configuration space to determine if it can send
>> TLPs to Root Port with the Relaxed Ordering Attributes set.
>>
>> The ixgbe driver could use this flag to determine if it can
>> send TLPs to Root Port with the Relaxed Ordering Attributes set.
>
> I'll let the Intel guys pick this up.
>
Thanks David, but I am not sure when the Intel guys would take over,
just Alex has replied, so I will release a new version according Alex's
suggestion.
> .
>
prev parent reply other threads:[~2017-08-17 1:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 9:41 Ding Tianhong
2017-08-16 9:41 ` [PATCH net 1/2] Revert commit 1a8b6d76dc5b ("net:add one common config...") Ding Tianhong
2017-08-16 9:41 ` [PATCH net 2/2] net: ixgbe: Use new IXGBE_FLAG2_ROOT_NO_RELAXED_ORDERING flag Ding Tianhong
2017-08-16 18:17 ` Alexander Duyck
2017-08-16 17:56 ` [PATCH net 0/2] net: ixgbe: Use new flag to disable Relaxed Ordering David Miller
2017-08-17 1:22 ` Ding Tianhong [this message]
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=ea51f2cc-49f7-3689-d503-23c56e6fe90b@huawei.com \
--to=dingtianhong@huawei.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sparclinux@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
all inboxes | Powered by JetHome®