From: Andi Kleen <andi@firstfloor.org>
To: Gavin McCullagh <Gavin.McCullagh@nuim.ie>
Cc: netdev@vger.kernel.org
Subject: Re: possible bug in tcp_probe
Date: Tue, 13 Nov 2007 14:28:08 +0100 [thread overview]
Message-ID: <p73ir46z34n.fsf@bingen.suse.de> (raw)
In-Reply-To: <20071113112615.GA7491@nuim.ie> (Gavin McCullagh's message of "Tue\, 13 Nov 2007 11\:26\:15 +0000")
Gavin McCullagh <Gavin.McCullagh@nuim.ie> writes:
> I'm using linux v2.6.22.6 and tcp_probe with a couple of small
> modifications[1].
>
> Even with moderately large numbers of flows (16 on the one machine) and
> increasingly as I monitor more flows than that, I get strange overflow
> problems such as this one:
You probably just need to increase the buffer (bufsize option to the
module or tcp_probe.bufsize if compiled in)
In general I think tcp_probe was always more intended a demo of how kprobes
could be used than a real production tool (with no offense to sch)
-Andi
next prev parent reply other threads:[~2007-11-13 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 11:26 possible bug in tcp_probe Gavin McCullagh
2007-11-13 13:02 ` Evgeniy Polyakov
2007-11-13 13:28 ` Andi Kleen [this message]
2007-11-13 14:59 ` SANGTAE HA
2007-11-13 15:20 ` Gavin McCullagh
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=p73ir46z34n.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=Gavin.McCullagh@nuim.ie \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).