All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: shemminger@linux-foundation.org
Cc: netdev@vger.kernel.org
Subject: Re: iproute2 showing wrong number of bytes on 64bit architectures.
Date: Tue, 10 Jul 2007 11:05:45 -0700 (PDT)	[thread overview]
Message-ID: <20070710.110545.112620737.davem@davemloft.net> (raw)
In-Reply-To: <20070710085640.128311d1@freepuppy.rosehill.hemminger.net>

From: Stephen Hemminger <shemminger@linux-foundation.org>
Date: Tue, 10 Jul 2007 08:56:40 -0700

> Looks like net_device_stats should have always used u32?

It used unsigned long ages ago, and ifconfig gets the bits
exported from /proc/net/dev output whereas we have to used
fixed data types in whatever we use over netlink so u32
was choosen.

  reply	other threads:[~2007-07-10 18:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 15:56 Fw: iproute2 showing wrong number of bytes on 64bit architectures Stephen Hemminger
2007-07-10 18:05 ` David Miller [this message]
2007-07-10 18:17   ` Chris Friesen
2007-07-10 18:36     ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2007-07-11 11:50 Andreas Henriksson
2009-01-13 14:14 Norman Rasmussen

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=20070710.110545.112620737.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.