From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x has finally made it!
Date: 13 Nov 2001 19:05:00 +0200 [thread overview]
Message-ID: <8Cn1lUxXw-B@khms.westfalen.de> (raw)
In-Reply-To: <20011113171836.A14967@emma1.emma.line.org>
In-Reply-To: <20011113171836.A14967@emma1.emma.line.org>
matthias.andree@stud.uni-dortmund.de (Matthias Andree) wrote on 13.11.01 in <20011113171836.A14967@emma1.emma.line.org>:
> On Tue, 13 Nov 2001, Alastair Stevens wrote:
>
> > For those who haven't seen it yet, Moshe Bar at BYTE.com has revisited his
> > Linux 2.4 vs FreeBSD benchmarks, using 2.4.12 in this case:
> >
> > http://www.byte.com/documents/s=1794/byt20011107s0001/1112_moshe.html
>
> Wow. That person is knowledgeable... NOT. Turning off fsync() for mail
> is just as good as piping it to /dev/null. See RFC-1123.
I rather think a non-fsync() system has a very much higher rate of
successful mail deliveries than a /dev/null one, and only slightly (if at
all) lower than a fsync() one.
Now, that slight difference *can* be rather important if you're a major
mail hub - or it can be below the noise level in an end user system. In
either case, however, *nobody* will accept /dev/null as an equivalent
substitute.
Well, nobody but you.
MfG Kai
next prev parent reply other threads:[~2001-11-13 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 10:12 Alastair Stevens
2001-11-13 16:18 ` Matthias Andree
2001-11-13 16:26 ` Christoph Hellwig
2001-11-13 16:30 ` Doug McNaught
2001-11-13 16:42 ` Matthias Andree
2001-11-13 17:15 ` Doug McNaught
2001-11-14 15:30 ` Matthias Andree
2001-11-13 17:05 ` Kai Henningsen [this message]
2001-11-13 19:49 ` Kevin Wooten
2001-11-14 6:18 ` Albert D. Cahalan
2001-11-14 11:22 ` Matthias Andree
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=8Cn1lUxXw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--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®