[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b6a2187b0801301823m331957e9n9d9bb9613622c844@mail.gmail.com>
Date: Thu, 31 Jan 2008 10:23:26 +0800
From: "Jeff Chua" <jeff.chua.linux@...il.com>
To: "Patrick McHardy" <kaber@...sh.net>
Cc: "Jozsef Kadlecsik" <kadlec@...ckhole.kfki.hu>,
lkml <linux-kernel@...r.kernel.org>,
"Krzysztof Piotr Oledzki" <ole@....pl>,
"David S. Miller" <davem@...emloft.net>,
cups-bugs <cups-bugs@...ysw.com>,
"Netfilter Development Mailinglist" <netfilter-devel@...r.kernel.org>
Subject: Re: cups slow on linux-2.6.24
On Jan 30, 2008 9:47 PM, Patrick McHardy <kaber@...sh.net> wrote:
> 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.
Attached. Again, both runs with this command to print ...
for((i=1; i<1001;i++)); do echo $i | lpr -Plp; done
In the good file (lo.good), look for this timestamp (08:38:11.818587)
when it paused then continue again at 08:38:22.477261. That's almost
11 seconds of "sleep" ... (may be a feature of TCP/IP?).
In the bad file (lo.bad), look for 08:47:55.434722 where it paused,
and then continue at
08:48:24.449176. That's 28 seconds of sleep. But, after it continued,
lpstat shows it's printing a job every 3 seconds. All 100 jobs take
approx 1400 seconds to complete as compared to under 100 seconds for
the good run.
Again, using latest linux, one with
17311393f969090ab060540bd9dbe7dc885a76d5 reverted, and the other
without.
Thanks,
Jeff.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists