linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kingsley G. Morse Jr." <change@nas.com>
To: akpm@zip.com.au
Cc: andrea@suse.de, linux-mm@kvack.org
Subject: Faster TCP wakeups
Date: Tue, 1 Oct 2002 15:50:46 -0700	[thread overview]
Message-ID: <20021001155046.A23683@debian1.loaner.com> (raw)

Hail Andrew,

I don't think we've met, but my name is Kingsley
G. Morse Jr. and first of all, I'd like to thank
you for improving the Linux kernel. I'm
benchmarking it.

I noticed in Kernel Traffic #186 that you've
converted TCP/IPV4 over to use faster wakeups.

This intrigues me, because I suspect TCP code is
degrading my computer's performance over time, and
perhaps other peoples' too.

My benchmarking found that after being up for 10
days, my computer's slowness is MOST correlated to
how often slab pages are allocated for TCP open
requests. (see "cat /proc/slabinfo")

In other words, the more often slab pages are
allocated for tcp open requests, the slower my
computer gets. 

The correlation coefficient is 0.62, which is on a
scale of -1 to 1. 

I believe it's noteworthy that 0.62 is higher than
any of the hundreds of other memory measures that
I've statistically analyzed.

It's also higher after 10 days of uptime.  Just
after booting, it's only 0.11. 

I suspect a TCP bug is causing fragmentation or
some other problem that gets worse over time.

Cheers,
Kingsley

PS: My computer has 

    64 MB or RAM
    1 GB of swap
    200 MHZ Pentium Pro
    2.4.19-aa

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

                 reply	other threads:[~2002-10-01 22:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021001155046.A23683@debian1.loaner.com \
    --to=change@nas.com \
    --cc=akpm@zip.com.au \
    --cc=andrea@suse.de \
    --cc=linux-mm@kvack.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