From: Patrick McHardy <kaber@trash.net>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
lkml <linux-kernel@vger.kernel.org>,
Krzysztof Piotr Oledzki <ole@ans.pl>,
"David S. Miller" <davem@davemloft.net>,
cups-bugs <cups-bugs@easysw.com>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: cups slow on linux-2.6.24
Date: Wed, 30 Jan 2008 14:47:22 +0100 [thread overview]
Message-ID: <47A07FEA.3000702@trash.net> (raw)
In-Reply-To: <b6a2187b0801291924k15f883aeg54f704156e4f2e3e@mail.gmail.com>
Jeff Chua wrote:
> On Jan 29, 2008 6:53 PM, Jozsef Kadlecsik <kadlec@blackhole.kfki.hu> wrote:
>
>> As the problem can be reproduced so easily, could you capture a full TCP
>> session and send the pcap file? Thus it could be analyzed, replayed, etc.
>> and found the reason why the patch above slows down the printing.
>> By reverting back it we loose TCP reopening support.
>
> Not an expert here. I use 'tcpdump -i lo' and don't see anything
> different between the good and bad. Anyway, attached are the good and
> bad log files.
>
> There's a slight pause of 27 seconds after 502 jobs (both good and bad
> runs), then the good one will resume and transmit in burst until
> completing all the 1000 times. The bad run will resume and transmit
> one-by-one every 3 seconds.
>
> Please tell me what options to use with tcpdump to dump more useful output.
A binary dump would be more useful:
tcpdump -i lo -w <outfile>
and I guess Jozsef also wants "-s 0" so the full packets are included.
next prev parent reply other threads:[~2008-01-30 13:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0801290635001.23096@boston.corp.fedex.com>
2008-01-28 22:56 ` cups slow on linux-2.6.24 Krzysztof Oledzki
[not found] ` <Pine.LNX.4.64.0801282348440.30640-2hlNpRK6mjE3b3fIMdp3XWZHpeb/A1Y/@public.gmane.org>
2008-01-28 23:55 ` Jeff Chua
[not found] ` <Pine.LNX.4.64.0801290855360.19273@blackhole.kfki.hu>
[not found] ` <b6a2187b0801291924k15f883aeg54f704156e4f2e3e@mail.gmail.com>
2008-01-30 13:47 ` Patrick McHardy [this message]
2008-01-31 2:23 ` Jeff Chua
[not found] ` <b6a2187b0801301823m331957e9n9d9bb9613622c844-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-01-31 2:26 ` Jeff Chua
2008-01-31 2:41 ` Patrick McHardy
[not found] ` <47A13573.7090804-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>
2008-01-31 3:21 ` Jeff Chua
[not found] ` <b6a2187b0801301921s4a7842cg6cfec09a393cd63-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-01-31 3:25 ` Patrick McHardy
2008-01-31 5:01 ` Jeff Chua
[not found] ` <b6a2187b0801302101l46d614c9y53f798a025b57dc3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-01-31 10:40 ` Jozsef Kadlecsik
2008-01-31 18:53 ` Patrick McHardy
2008-02-01 0:47 ` David Newall
2008-02-01 2:12 ` David Miller
2008-02-01 6:07 ` David Newall
2008-02-01 6:10 ` Patrick McHardy
2008-02-01 5:28 ` Jeff Chua
2008-02-02 14:44 ` Jozsef Kadlecsik
2008-02-03 16:08 ` Jeff Chua
2008-01-31 2:31 ` Jeff Chua
[not found] <Pine.LNX.4.64.0802042226340.28805@boston.corp.fedex.com>
[not found] ` <Pine.LNX.4.64.0802042226340.28805-2K9XAwmnW1wYQUuIRqa960M9+F4ksjoh@public.gmane.org>
2008-02-04 20:17 ` Jozsef Kadlecsik
2008-02-05 1:17 Jeff Chua
[not found] ` <Pine.LNX.4.64.0802050913560.6704-2K9XAwmnW1wYQUuIRqa960M9+F4ksjoh@public.gmane.org>
2008-02-05 8:16 ` Jozsef Kadlecsik
2008-02-05 13:47 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2008-02-10 15:06 Jeff Chua
[not found] ` <Pine.LNX.4.64.0802102257420.14442-2K9XAwmnW1wYQUuIRqa960M9+F4ksjoh@public.gmane.org>
2008-02-14 15:02 ` Jozsef Kadlecsik
2008-02-14 22:50 ` David Miller
2008-02-15 1:44 ` Patrick McHardy
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=47A07FEA.3000702@trash.net \
--to=kaber@trash.net \
--cc=cups-bugs@easysw.com \
--cc=davem@davemloft.net \
--cc=jeff.chua.linux@gmail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=ole@ans.pl \
/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).