mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: linux@horizon.com
To: linux-kernel@vger.kernel.org, Valdis.Kletnieks@vt.edu
Subject: Re: Reiser4 Inclusion
Date: 17 Jul 2006 18:34:23 -0400	[thread overview]
Message-ID: <20060717223423.24205.qmail@science.horizon.com> (raw)

>> I have deployed two nearly identical servers in Florida (I live in
>> Washington state) but one difference: one uses ext3 and the other
>> reiser4. The ping time of the reiser4 server is (on average) 20ms faster
>> than the ext3 server.
>
> OK, I'll bite.  What *POSSIBLE* reason is there for the choice of filesystem
> to matter to an ICMP Echo Request/Reply?  I'm suspecting something else,
> like the ext3 server needs to re-ARP before sending the Echo Reply, or some
> such.

Er... I was assuming that was an application-level ping, e.g. "fetch
database-generated web page", and not an ICMP-level ping.

If this *is* talking about ICMP-level ping, I agree completely;
that makes no sense.  Either there is a dire bug in Linux networking,
or the networks aren't the same.  Assuming the two machines are
located together (if they're not, there's your problem right there),
is the same 20 ms visible when you ping them from each other?

             reply	other threads:[~2006-07-17 22:34 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 22:34 linux [this message]
     [not found] <06Jul25.011533edt.35900@gpu.utcc.utoronto.ca>
2006-07-30 22:02 ` Tilman Schmidt
  -- strict thread matches above, loose matches on Subject: below --
2006-07-17  3:02 Caleb Gray
2006-07-17  9:25 ` Arjan van de Ven
2006-07-17 11:48   ` Grzegorz Kulewski
2006-07-17 11:57     ` Alexander Gran
2006-07-17 14:06     ` Diego Calleja
2006-07-17 14:31       ` Grzegorz Kulewski
2006-07-17 15:51         ` Matthias Andree
2006-07-18  7:59           ` Jan Engelhardt
2006-07-18 20:47             ` Matthias Andree
2006-07-19  1:19               ` Joshua Hudson
2006-07-19  9:27               ` Tilman Schmidt
2006-07-19 11:00                 ` Krzysztof Halasa
2006-07-19 11:03                 ` Pekka Enberg
2006-07-19 15:32                   ` Tilman Schmidt
2006-07-19 19:04                     ` Valdis.Kletnieks
2006-07-19 19:12                       ` Tilman Schmidt
2006-07-19 20:09                         ` Valdis.Kletnieks
2006-07-19 22:36                           ` Tilman Schmidt
2006-07-19 20:29                       ` Jeff V. Merkey
2006-07-19 22:01                         ` Matthias Andree
2006-07-19 22:34                     ` Helge Hafting
2006-07-17 15:52         ` gmu 2k6
2006-07-17 15:57           ` Alexander Gran
2006-07-17 19:01         ` Horst von Brand
2006-07-17 15:13     ` Jeff Anderson-Lee
2006-07-17 15:56       ` Matthias Andree
2006-07-17 20:48       ` Erik Mouw
2006-07-18  0:49         ` Jeff Dike
2006-07-18 11:43           ` Christoph Hellwig
2006-07-17  9:44 ` Patrick McFarland
2006-07-17 11:07 ` Diego Calleja
2006-07-17 14:38 ` Alex Riesen
2006-07-17 18:05 ` Valdis.Kletnieks
2006-07-18 23:10   ` Nix

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=20060717223423.24205.qmail@science.horizon.com \
    --to=linux@horizon.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --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

all inboxes | Powered by JetHome®