From: Stephen Hemminger <shemminger@vyatta.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: Re: PF_ring and friends: Options for making Linux suck less when capturing packets
Date: Wed, 19 Oct 2011 09:52:44 -0700 [thread overview]
Message-ID: <20111019095244.27354f74@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAA93jw7os4NkvyU_33422H6Ag=6diipPnQ5cfSnUoen+eUYO9Q@mail.gmail.com>
On Wed, 19 Oct 2011 18:44:08 +0200
Dave Taht <dave.taht@gmail.com> wrote:
> Currently I can do tcpdump -i eth1 -s 200 -w /some/usb/stick.cap at about
> 1.2 - 2MB/sec before saturating cpu on the wndr3700v2. (MB =megabyte)
>
> I can r/w a usb stick at about 8/7 MB/sec. I haven' tried a 'real' hard
> disk.
>
> About 50Mbit/sec I figure covers the 95 percentile of most home users to
> their ISP. 100Mbit would be better. Being drop-free would be really helpful
> on shorter tests....
>
> I was also thinking about an in-kernel module that uses 'splice' to send the
> data to a file... as well as the current jit work for bpf, using netfilter,
> and various other alternatives.
>
> Or writing something in a iptables or tc filter to track things more sanely
> that web100 does....
>
> Ideas?
USB sticks are real slow. Even some infinitely fast capture isn't going
to get around that. Get a real SSD and put it in enclosure that supports
USB 3.0?
next prev parent reply other threads:[~2011-10-19 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 16:44 Dave Taht
2011-10-19 16:52 ` Stephen Hemminger [this message]
2011-10-19 17:23 ` Hal Murray
2011-11-05 11:30 ` Petri Rosenström
2011-10-19 17:02 ` Jim Gettys
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=20111019095244.27354f74@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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