public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Netfilter <netfilter@us5.samba.org>
Subject: Re: test13-pre1 changelog
Date: Fri, 15 Dec 2000 09:30:16 -0500	[thread overview]
Message-ID: <20001215093016.S26953@ns> (raw)
In-Reply-To: <Pine.LNX.4.10.10012141552180.12695-100000@penguin.transmeta.com> <Pine.LNX.4.30.0012142244200.27741-100000@waste.org>
In-Reply-To: <Pine.LNX.4.30.0012142244200.27741-100000@waste.org>; from oxymoron@waste.org on Thu, Dec 14, 2000 at 10:58:05PM -0600

[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]

* Oliver Xymoron (oxymoron@waste.org) wrote:
> On Thu, 14 Dec 2000, Linus Torvalds wrote:
> 
> > A 100ms delay sounds like some interrupt shut up or similar (and then
> > timer handling makes it limp along).
> 
> Possibly related datapoint: after several days of uptime, my
> 2.4.0-test10pre? machine went into some sort of slow mode after coming
> back from suspend (and doing an /etc/init.d/networking restart). Symptoms
> seemed to be extra second or so setting up a TCP connection. Ping, etc.,
> appeared to work just fine, no packet loss apparent, bandwidth looked good
> too. Sadly I had to do actual work that required zippy web access, so I
> rebooted rather than doing a thorough diagnostic. This is a VAIO with
> compiled in eepro100, no special networking options.

	Actually, I figured out what it was and I feel kind of stupid, and
suprised.  I knew I should have tried rebooting before complaining.  It
turns out it actually was something in my firewall rules, it appears that
for every logged packet there is something along the lines of a 100ms
delay that gets added on.

	Not sure if that is something that could be easily fixed or not, or
perhaps I'm doing something wrong, but that seems unlikely since all I
changed was if it jumped to the LOG chain or not.

		Stephen

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2000-12-15 15:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-14 20:06 test13-pre1 changelog David Riley
2000-12-14 20:11 ` Dr. Kelsey Hudson
2000-12-14 20:39   ` Frank Davis
2000-12-14 20:44     ` Jeff Garzik
2000-12-14 22:16   ` Marty Pitts
2000-12-14 23:31 ` Linus Torvalds
2000-12-14 23:45   ` Stephen Frost
2000-12-14 23:51     ` Alan Cox
2000-12-14 23:56       ` Stephen Frost
2000-12-15  0:06         ` Linus Torvalds
2000-12-15  0:17           ` Stephen Frost
2000-12-14 23:56     ` Linus Torvalds
2000-12-15  0:10       ` Stephen Frost
2000-12-15  0:20         ` Linus Torvalds
2000-12-15  4:58       ` Oliver Xymoron
2000-12-15 14:30         ` Stephen Frost [this message]
2000-12-15 15:09           ` Oliver Xymoron
2000-12-15  8:45   ` Pau
2000-12-15 15:37   ` Tom Rini
2000-12-15 17:10     ` Linus Torvalds
2000-12-15 18:04       ` Alan Cox
2000-12-15 18:08         ` Linus Torvalds
2000-12-15 18:22           ` Alexander Viro
2000-12-15 18:32           ` Alan Cox

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=20001215093016.S26953@ns \
    --to=sfrost@snowman.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter@us5.samba.org \
    --cc=oxymoron@waste.org \
    --cc=torvalds@transmeta.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