public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel 2.2.20-pre10 Initial Impressions
Date: Tue, 25 Sep 2001 02:41:57 -0700	[thread overview]
Message-ID: <20010925024157.E8738@mikef-linux.matchmail.com> (raw)
In-Reply-To: <3BAC8E1C.2201.524EE2@localhost> <3BAE3F75.665.75F16A@localhost>
In-Reply-To: <3BAE3F75.665.75F16A@localhost>

On Sun, Sep 23, 2001 at 08:00:53PM -0500, John L. Males wrote:
Content-Description: Mail message body
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi Alan,
> 
> Test Case One:
> ****************
> 
> - - Start Netscape 4.78 from desktop ICON
> - - Click the pull down arrow on far right side of the "Go To:" (AKA
> URL line) of Netscape 4.78.
> 
> Results:
> All were instant response from Netscape.  Did the test for each

> Test Case Two:
> *****************
> 
> Steps used:
> 
> - - Boot System
> - - Log onto non-root user id.
> - - "startx" (KDE desktop started)
> (applications prestart from last log off include kppp, kpppload,
> xosview, gnome terminal, khrono, 3 kfm's)
> - - Had kppp "connect" to my ISP (dial up model 56KB, really 49,300
> most of time, some connects 48,000, note kppp is configured to start
> up ntpdate to sync with some time servers.)
> - - Start Netscape 4.78 from desktop ICON
> - - Click the pull down arrow on far right side of the "Go To:" (AKA
> URL line) of Netscape 4.78.
> 
> Results:
> 
> For Kernel 2.2.19OWL, 2.2.20-pre10, 2.4.9-ac10
> 
> All times were 2 minutes 3 seconds to get the URL list that appears
> 
> 

> Test Case Three:
> *******************
> 
> For the two times this test case was also done, still a delay of 2
> minutes 3 seconds from the time clicked the button until the URLs
> appeared.

> Test Case Four:
> ******************
> 
> For the one time I did this test case, a delay of 2 minutes 19
> seconds from the time clicked the button until the URLs appeared.
> 
> 

> Test Case Five:
> *****************
> For Kernel 2.2.19OWL only was this test done.  First time the delay
> was 2 minutes 3 seconds, the second time it was 2 minutes 15 seconds.
> 
> 

I think you're right, it's not a kernel issue.  You should run "tcpdump -qni
ppp0" in a xterm before you start netscape.

You will probably see dns requests going out.  You should check to make sure
that you are not blocking incomming udp ports (1024-5000 for bind, not sure
about resolver...) as that would lengthen the response time considerably if
only a few are open, and completely stop you if all are blocked.

Mike

  reply	other threads:[~2001-09-25  9:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-19  4:26 Linux Kernel 2.2.20-pre10 Initial Impressions John L. Males
2001-09-22 16:35 ` Alan Cox
2001-09-22 18:11   ` Re[03]: " John L. Males
2001-09-22 19:00     ` Alan Cox
2001-09-24  1:00       ` Re[05]: " John L. Males
2001-09-25  9:41         ` Mike Fedyk [this message]
2001-09-22 18:20   ` Re[03]: " John L. Males
2001-09-24 21:02 ` Tim Moore
2001-09-25  1:25   ` Re[06]: " John L. Males
  -- strict thread matches above, loose matches on Subject: below --
2001-09-26  4:43 Re[07]: " John L. Males
2001-09-26 19:50 ` Tim Moore

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=20010925024157.E8738@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=linux-kernel@vger.kernel.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