From: Ben Greear <greearb@candelatech.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: cfriesen@nortelnetworks.com, linux-kernel@vger.kernel.org
Subject: Re: how to get per-socket stats on udp rx buffer overflow?
Date: Wed, 29 May 2002 08:30:41 -0700 [thread overview]
Message-ID: <3CF4F421.1040908@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205290640580.4572-100000@w-nivedita2.des.beaverton.ibm.com>
Nivedita Singhvi wrote:
> On Tue, 28 May 2002, Ben Greear wrote:
>>It would not be that expensive..it's just an extra counter that
>>is bumped whenever a pkt is dropped.
>>
>
> True for one counter, but generally when considering per
> socket stats as a feature, you include all the TCP/UDP/I
> stats, and if youre not holding locks, thats probably an
> atomic increment. Pretty soon we're talking actual
> performance and scalability money. (Even if we're not
> in the mindset of saving every cycle wherever possible).
Integer increments are usually pretty cheap. Considering
accuracy is not absolutely needed (imho), then there is no
need to lock or use special atomic increments.
So, I view the performance issue as not that big of a deal. Space
may be a bigger deal, and the /proc interface and/or IOCTLs to read
the counters...
If/when I do implement, I'll be sure to make it a selectable option
in the kernel config process...
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-05-29 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-25 2:59 how to get per-socket stats on udp rx buffer overflow? Nivedita Singhvi
2002-05-28 20:52 ` Ben Greear
2002-05-29 13:58 ` Nivedita Singhvi
2002-05-29 15:30 ` Ben Greear [this message]
2002-05-29 18:59 ` Nivedita Singhvi
-- strict thread matches above, loose matches on Subject: below --
2002-05-24 20:59 Chris Friesen
2002-05-24 20:54 ` David S. Miller
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=3CF4F421.1040908@candelatech.com \
--to=greearb@candelatech.com \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=niv@us.ibm.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