From: rwhron@earthlink.net
To: rml@tech9.net
Cc: linux-kernel@vger.kernel.org, jamagallon@able.es
Subject: Re: [PATCHSET] Linux 2.4.19-pre8-jam2
Date: Mon, 13 May 2002 18:45:06 -0400 [thread overview]
Message-ID: <20020513184506.A27038@rushmore> (raw)
> > > - Re-introduction of wake_up_sync to make pipes run fast again. No idea
> > > about this is useful or not, that is the point, to test it (Randy ?)
> > 2.5 kernels <= 2.5.15 aren't completing umount on the 4 way Xeon.
> Is umount not completing somehow due to the lack of wake_up_sync ???
The umount issue is unrelated to wake_up_sync. Could be a scsi driver
issue, as 2.5.x has been fine on my IDE system. Before the benchmarks,
I mkfs some filesystems and mount and umount them. Haven't
been able to get past that point with 2.5.x yet.
> Fwiw, I am not sold that reintroducing wake_up_sync is worth it. The
> benchmark is synthetic and could very well not represent the general
> case in which the load balancer is capable of handling the scenario
> without the hackery of an explicit sync option.
That could well be. The kernel build test which applies patches
and compiles with -pipe is as close as I have to a general pipe
test. The kernel build test has a low variability (~2%) between
any of the kernels tested on the 4 way box.
It's worth testing wake_up_sync though. Occasionally there's
a surprise.
--
Randy Hron
next reply other threads:[~2002-05-13 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 22:45 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-13 11:45 [PATCHSET] Linux 2.4.19-pre8-jam2 rwhron
2002-05-13 16:29 ` Robert Love
2002-05-13 0:06 J.A. Magallon
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=20020513184506.A27038@rushmore \
--to=rwhron@earthlink.net \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.