From: Zumeng Chen <zumeng.chen@gmail.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: Netdev <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Siva Reddy Kallam <siva.kallam@broadcom.com>,
"michael.chan@broadcom.com" <mchan@broadcom.com>,
"prashant.sreedharan@broadcom.com" <prashant@broadcom.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 1/1] tg3: fix meaningless hw_stats reading after tg3_halt memset 0 hw_stats
Date: Sun, 29 Apr 2018 14:43:19 +0800 [thread overview]
Message-ID: <eb6f9052-88fc-6b90-2278-88df3b3cccd8@gmail.com> (raw)
In-Reply-To: <CACKFLi=UxiSUAx8CoMKpx16d7mVSAbbmhR-m=1W_kzNrePu7XQ@mail.gmail.com>
On 2018年04月29日 02:36, Michael Chan wrote:
> On Fri, Apr 27, 2018 at 8:15 PM, Zumeng Chen <zumeng.chen@gmail.com> wrote:
>
>> diff --git a/drivers/net/ethernet/broadcom/tg3.h b/drivers/net/ethernet/broadcom/tg3.h
>> index 3b5e98e..6727d93 100644
>> --- a/drivers/net/ethernet/broadcom/tg3.h
>> +++ b/drivers/net/ethernet/broadcom/tg3.h
>> @@ -3352,6 +3352,7 @@ struct tg3 {
>> struct pci_dev *pdev_peer;
>>
>> struct tg3_hw_stats *hw_stats;
>> + bool hw_stats_flag;
> You can just add another bit to enum TG3_FLAGS for this purpose.
Right, it's a good idea, I didn't notice it, I'll send V2 with that later.
>
> While this scheme will probably work, I think a better and more
> elegant way to fix this is to use RCU.
IMHO, RCU is not necessary for this simple two consumers, and no
frequent ops
on tg3_halt, plus no new locker involved either.
Cheers,
Zumeng
>
>> dma_addr_t stats_mapping;
>> struct work_struct reset_task;
>>
>> --
>> 2.9.3
>>
prev parent reply other threads:[~2018-04-29 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 3:15 [PATCH 1/1] tg3: fix meaningless hw_stats reading after tg3_halt memset 0 hw_stats Zumeng Chen
2018-04-28 18:36 ` Michael Chan
2018-04-29 6:43 ` Zumeng Chen [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=eb6f9052-88fc-6b90-2278-88df3b3cccd8@gmail.com \
--to=zumeng.chen@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=prashant@broadcom.com \
--cc=siva.kallam@broadcom.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).