From: N N Ashok <nalkunda@cse.msu.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc stats
Date: Mon, 28 Jul 2003 20:22:06 +0000 [thread overview]
Message-ID: <marc-lartc-105942432025200@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105917681726671@msgid-missing>
On Monday 28 July 2003 13:49, Stef Coene scrawled:
> On Saturday 26 July 2003 01:46, Rajesh Srivastava wrote:
> > Hi,
> >
> > I am getting negative sent bytes count in tc stats after transmitting
> > over 1 GB of data. It seems like a counter size issue. Is there a fix for
> > this?
>
> I don't think so.
>
> Stef
The bytes count in tc_stats is __u64 type so it wont overflow after 1GB also.
Ashok
--
-----------------------------------------------------------------------------
N N Ashok
East Lansing, MI-48823
Ph: 408-644-3646 (c)
517-353-4633 (eLANS Lab)
517-355-1789 (ERL Lab)
-----------------------------------------------------------------------------
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-07-28 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 23:46 [LARTC] tc stats Rajesh Srivastava
2003-07-28 17:49 ` Stef Coene
2003-07-28 20:22 ` N N Ashok [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=marc-lartc-105942432025200@msgid-missing \
--to=nalkunda@cse.msu.edu \
--cc=lartc@vger.kernel.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