From: "Martin Hundebøll" <martin@hundeboll.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Add get_ethtool_stats() support
Date: Tue, 17 Apr 2012 15:24:48 +0200 [thread overview]
Message-ID: <4F8D6F20.8060501@hundeboll.net> (raw)
In-Reply-To: <201204171019.32919.lindner_marek@yahoo.de>
Hi Marek,
On 04/17/2012 10:19 AM, Marek Lindner wrote:
> On Tuesday, April 17, 2012 01:24:55 Martin Hundebøll wrote:
>> Added additional counters in a bat_stats structure, which are exported
>> through the ethtool api. The counters are specific to batman-adv and
>> includes:
>> forwarded packets
>> management packets (OGMs at this point)
>> translation table packets
>> distributed arp table packets
>
> Looks very good! A few questions though:
>
>
>> @@ -869,6 +875,9 @@ static int route_unicast_packet(struct sk_buff *skb,
>> struct hard_iface *recv_if) /* decrement ttl */
>> unicast_packet->header.ttl--;
>>
>> + /* Update stats counter */
>> + bat_priv->bat_stats.forward++;
>
> Here we only count the number of packets. Would it be possible to also count
> the number of bytes ? Similar to tx_packets and tx_bytes ?
> Same for management tx/bytes.
Sure, if we want it, I can make it :)
>> +struct bat_stats {
>> + uint64_t forward;
>> + uint64_t mgmt_tx;
>> + uint64_t mgmt_rx;
>> + uint64_t tt_request_tx;
>> + uint64_t tt_request_rx;
>> + uint64_t tt_response_tx;
>> + uint64_t tt_response_rx;
>> + uint64_t tt_roam_adv_tx;
>> + uint64_t tt_roam_adv_rx;
>> + uint64_t dat_request_tx;
>> + uint64_t dat_request_rx;
>> + uint64_t dat_reply_tx;
>> + uint64_t dat_reply_rx;
>> +};
>
> How do we handle code segments that are not compiled into the module ? We
> simply leave this counters hanging around at 0 ?
As I understand it, ethtool doesn't mind "unused" counters in general, so it comes down to the memory footprint of batman-adv. Do we want to clutter the code with ifdef's to save the memory?
--
Kind Regards
Martin Hundebøll
Frederiks Allé 99A, 1.th
8000 Aarhus C
Denmark
+45 61 65 54 61
martin@hundeboll.net
next prev parent reply other threads:[~2012-04-17 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 23:24 [B.A.T.M.A.N.] [PATCH] batman-adv: Add get_ethtool_stats() support Martin Hundebøll
2012-04-17 7:12 ` Antonio Quartulli
2012-04-17 7:25 ` Antonio Quartulli
2012-04-17 13:22 ` Martin Hundebøll
2012-04-17 8:19 ` Marek Lindner
2012-04-17 13:24 ` Martin Hundebøll [this message]
2012-04-17 13:29 ` Antonio Quartulli
2012-04-17 16:52 ` [B.A.T.M.A.N.] [PATCHv2] " Martin Hundebøll
2012-04-18 13:35 ` [B.A.T.M.A.N.] [PATCHv3] " Martin Hundebøll
2012-04-20 8:13 ` Marek Lindner
2012-04-20 15:02 ` [B.A.T.M.A.N.] [PATCHv4] " Martin Hundebøll
2012-04-22 9:03 ` Marek Lindner
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=4F8D6F20.8060501@hundeboll.net \
--to=martin@hundeboll.net \
--cc=b.a.t.m.a.n@lists.open-mesh.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