public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <ordex@autistici.org>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<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:29:34 +0200	[thread overview]
Message-ID: <20120417132934.GD3377@ritirata.org> (raw)
In-Reply-To: <4F8D6F20.8060501@hundeboll.net>

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

On Tue, Apr 17, 2012 at 03:24:48PM +0200, Martin Hundebøll wrote:
> >> +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?

As we do for all the other component-private fields in bat_priv, I'd say that it
would be better to do the same here by using ifdefs.

Cheers,


-- 
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara

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

  reply	other threads:[~2012-04-17 13:29 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
2012-04-17 13:29     ` Antonio Quartulli [this message]
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=20120417132934.GD3377@ritirata.org \
    --to=ordex@autistici.org \
    --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