mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Terry Griffin <terryg@axian.com>
To: linux-kernel@vger.kernel.org
Subject: odd behavior with r8169 and pcap
Date: Mon, 29 Nov 2004 10:11:49 -0800	[thread overview]
Message-ID: <1101751909.2291.21.camel@tux.hq.axian.com> (raw)

Hi all,

I'm seeing some very strange behavior with the r8169 driver
in 2.6.9. (Also observed in FC2's 2.6.5-1).

Throughput is generally dog slow, less than 100Mb/s. But if
I fire up any libpcap-based monitoring utility (ethereal,
iftop, etc) the throughput suddenly jumps an order of magnitude
to near 1Gb/s. As soon as I quit from the monitoring utility
the throughput drops back back to where it was before. This can
be repeated over an over.

I created a dummy libpcap monitoring program (below). This
is enough to trigger the behavior.

So the obvious questions are: Is this a known problem? Why the
heck does it do this? Is there a fix or workaround to get the
high rate all the time other than running a pcap utility 24x7?

Thanks,
Terry Griffin

-- dummy-monitor.c -----------------

#include <pcap.h>
#define CAPTURE_LENGTH 68

void null_handler(u_char *user, const struct pcap_pkthdr *pkt_header,
                  const u_char *pkt_data)
{
}

int main( int argc, char *argv[] )
{
    char *iface;
    pcap_t* pd;
    char errbuf[PCAP_ERRBUF_SIZE];

    if( argc == 1 )
        iface = "eth0";
    else
        iface = argv[1];

    pd = pcap_open_live(iface,CAPTURE_LENGTH,0,1000,errbuf);
    pcap_loop(pd,-1,(pcap_handler)null_handler,NULL);

    return 0;
}



             reply	other threads:[~2004-11-29 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29 18:11 Terry Griffin [this message]
2004-11-29 21:02 ` Francois Romieu
2004-11-29 22:07   ` Terry Griffin
2004-11-29 23:18     ` Francois Romieu
2004-11-30  0:01       ` Terry Griffin
2004-11-30  0:21         ` Francois Romieu

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=1101751909.2291.21.camel@tux.hq.axian.com \
    --to=terryg@axian.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®