netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, hayeswang@realtek.com,
	ivecera@redhat.com, nic_swsd@realtek.com
Subject: Re: [PATCH v4 net-next] r8169: Add values missing in @get_stats64 from HW counters
Date: Wed, 26 Aug 2015 10:54:46 +0200	[thread overview]
Message-ID: <20150826085446.GA12087@calimero.vinschen.de> (raw)
In-Reply-To: <20150825225406.GA24297@electric-eye.fr.zoreil.com>

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

On Aug 26 00:54, Francois Romieu wrote:
> David Miller <davem@davemloft.net> :
> [...]
> > Your counter offsets should be read at probe time, not open time.
> 
> It can be done but the "CmdRxEnb / rx traffic must be enabled" constraint
> will make it a major pita. 
> 
> Reading counter offsets at the end of open() naturally solves this
> constraint (retentive error unwinding in opne() stops being completely
> trivial though :o/ ).
> 
> > Bringing the interface is brought down/up should not reset the
> > counters.
> 
> Afaiks rtl8169_tc_offsets.inited in rtl8169_init_counter_offsets
> takes care of it: it's set during the first open() after probe().
> 
> Looking at it again, the patch directly stores 16 and 32 bit values
> in rtnl_link_stats64. Nobody should care about exact exceedingly high
> error count but rx_multicast ought to be accumulated.

I'll have a look into that for a followup patch.


Thanks,
Corinna

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2015-08-26  8:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  9:04 [PATCH] r8169: Add values missing in @get_stats64 from HW counters Corinna Vinschen
2015-08-18 21:40 ` Francois Romieu
2015-08-19  2:05   ` David Miller
2015-08-19  9:10     ` Corinna Vinschen
2015-08-19  2:51   ` Hayes Wang
2015-08-19  9:13     ` Corinna Vinschen
2015-08-19  9:31       ` Hayes Wang
2015-08-19 13:07         ` Corinna Vinschen
2015-08-19 14:24           ` Corinna Vinschen
2015-08-19 19:24             ` Corinna Vinschen
2015-08-20  2:43               ` Hayes Wang
2015-08-20  9:41                 ` Corinna Vinschen
2015-08-20  9:56                   ` Hayes Wang
2015-08-21 10:09 ` [PATCH v2 net-next] " Corinna Vinschen
2015-08-21 10:24   ` Corinna Vinschen
2015-08-21 19:39   ` Francois Romieu
2015-08-21 22:07     ` Corinna Vinschen
2015-08-21 23:59       ` Francois Romieu
2015-08-22  8:39         ` Corinna Vinschen
2015-08-22 11:23           ` Francois Romieu
2015-08-24  7:33             ` Corinna Vinschen
2015-08-24 10:29               ` Corinna Vinschen
2015-08-24 23:33               ` Francois Romieu
2015-08-25  8:39                 ` Corinna Vinschen
2015-08-25 21:14                   ` Francois Romieu
2015-08-24 10:27 ` [PATCH v3 " Corinna Vinschen
2015-08-24 10:52 ` [PATCH v4 " Corinna Vinschen
2015-08-25 21:15   ` David Miller
2015-08-25 22:54     ` Francois Romieu
2015-08-25 22:59       ` David Miller
2015-08-25 23:03         ` David Miller
2015-08-26  8:55           ` Corinna Vinschen
2015-08-26  8:54       ` Corinna Vinschen [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=20150826085446.GA12087@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=davem@davemloft.net \
    --cc=hayeswang@realtek.com \
    --cc=ivecera@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=romieu@fr.zoreil.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).