From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Wei Yang <weiyang@linux.vnet.ibm.com>,
Amir Vadai <amirv@mellanox.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: Face some error after applying commit 7dfa4b414d4(net/mlx4_en: Code cleanups in tx path)
Date: Mon, 10 Nov 2014 09:59:33 +0800 [thread overview]
Message-ID: <20141110015933.GB6294@richard> (raw)
In-Reply-To: <CANn89i+ekXHJSePzQ0rWx2KKqwYGTrok3-ZZ1RdEygVJcGDqRQ@mail.gmail.com>
On Fri, Nov 07, 2014 at 07:38:15PM -0800, Eric Dumazet wrote:
>On Fri, Nov 7, 2014 at 6:57 PM, Wei Yang <weiyang@linux.vnet.ibm.com> wrote:
>> Eric and Amir
>>
>> I am testing the VF on PowerNV platform with 3.18-rc2.
>> After applying this patch I face some errors.
>>
>> First is the compiling error.
>>
>> drivers/net/ethernet/mellanox/mlx4//en_tx.c: In function ‘mlx4_en_xmit’:
>> drivers/net/ethernet/mellanox/mlx4//en_tx.c:802:8: error: ‘shinfo’ undeclared (first use in this function)
>> shinfo->tx_flags & SKBTX_HW_TSTAMP)) {
>> ^
>> include/linux/compiler.h:160:42: note: in definition of macro ‘unlikely’
>> # define unlikely(x) __builtin_expect(!!(x), 0)
>> ^
>> drivers/net/ethernet/mellanox/mlx4//en_tx.c:802:8: note: each undeclared identifier is reported only once for each function it appears in
>> shinfo->tx_flags & SKBTX_HW_TSTAMP)) {
>> ^
>> include/linux/compiler.h:160:42: note: in definition of macro ‘unlikely’
>> # define unlikely(x) __builtin_expect(!!(x), 0)
>> ^
>> make[1]: *** [drivers/net/ethernet/mellanox/mlx4//en_tx.o] Error 1
>> make: *** [_module_drivers/net/ethernet/mellanox/mlx4/] Error 2
>>
>
>
>This compilation error seems strange.
>
>Are you sure your tree is pristine, not corrupted in any way ?
I believe I did the revert one by one with git revert.
>
>
>> I tried to fix this with following change:
>>
>> [root@tian-lp1 3.18]# git diff
>> diff --git a/drivers/net/ethernet/mellanox/mlx4/en_tx.c b/drivers/net/ethernet/m
>> index eaf23eb..d2f06a7 100644
>> --- a/drivers/net/ethernet/mellanox/mlx4/en_tx.c
>> +++ b/drivers/net/ethernet/mellanox/mlx4/en_tx.c
>> @@ -799,8 +799,8 @@ netdev_tx_t mlx4_en_xmit(struct sk_buff *skb, struct net_dev
>> * set flag for further reference
>> */
>> if (unlikely(ring->hwtstamp_tx_type == HWTSTAMP_TX_ON &&
>> - shinfo->tx_flags & SKBTX_HW_TSTAMP)) {
>> - shinfo->tx_flags |= SKBTX_IN_PROGRESS;
>> + skb_shinfo(skb)->tx_flags & SKBTX_HW_TSTAMP)) {
>> + skb_shinfo(skb)->tx_flags |= SKBTX_IN_PROGRESS;
>> tx_info->ts_requested = 1;
>> }
>>
>> But seems to face another error.
>>
>
>I suspect your tree is not the official tree, I do not see how you got
>this compilation error.
I checked the upstream git tree again, and find this commit:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7dfa4b414d4eec8da56e44fb2b4aea3e549b092f
And I want to say the shinfo local variable is introduced in commit:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b9d8839a44092cb4268ef2813c34d5dbf3363603
And in my log tree, also checked the upstream, this one is applyed after the
first one. And the compiling error will disappear untill I apply this one.
So this compiling issue can't reproduced at your side? You have reset --hard
to the "Code cleanup" one, and can't see the error? That is strange.
--
Richard Yang
Help you, Help me
next parent reply other threads:[~2014-11-10 1:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141108025758.GA13875@richard>
[not found] ` <CANn89i+ekXHJSePzQ0rWx2KKqwYGTrok3-ZZ1RdEygVJcGDqRQ@mail.gmail.com>
2014-11-10 1:59 ` Wei Yang [this message]
2014-11-10 2:07 ` Face some error after applying commit 7dfa4b414d4(net/mlx4_en: Code cleanups in tx path) Wei Yang
2014-11-10 2:46 ` Eric Dumazet
2014-11-10 5:40 ` Wei Yang
2014-11-10 8:00 ` Amir Vadai
2014-11-11 1:57 ` Wei Yang
2014-11-11 6:49 ` Or Gerlitz
2014-11-11 7:28 ` Amir Vadai
2014-11-11 7:42 ` Wei Yang
2014-11-11 8:40 ` Amir Vadai
2014-11-11 9:12 ` Wei Yang
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=20141110015933.GB6294@richard \
--to=weiyang@linux.vnet.ibm.com \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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).