From: "Samium Gromoff" <_deepfire@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: O_DIRECT! or O_DIRECT?
Date: Wed, 04 Jul 2001 00:34:35 +0400 [thread overview]
Message-ID: <E15HWsV-0000lM-00@f12.port.ru> (raw)
HI folks, sometime ago i seen on lkml a post
from >< regarding the implementation of O_DIRECT.
The thing about to care, is the fact, that *nobody*,
reacted on this post. It seems to me that nobody was
happy enough about this to tell "oh yes! at last!"
This is interesting, because one real advantage
of O_DIRECT are these greased weasel fast 15-20 Mb/s
file copies, which ones makes windoze users to look
on us as on lesser beings.
I understand, though, that this approach scales
bad in the terms of multithread loads, which ones are
especially important in server environments, the place
linux initially growed from, and that is why it wasn`t
already implemented.
One more problem i see here, and i think it is an
*extremely* important one, that making open( ... ,
BLA_BLA_BLA | O_DIRECT) is a thing some people may
overspeculate with. I mean that implementing O_DIRECT
in cp(1), wins the prize, but in the case of, say,
find(1) it is definitely not a wise move. The problem
may be determined as "poisoning" software with this
godblessed O_DIRECT, to the state, when 70% of code
on an average machine will use it, thus *completely*
killing the advantages of buffered access, and
suddenly *bang!*: the overall performance is died.
But the worst thing, is what the process of
poisoning is completely uncontrollable: each
stupid doodie can think, that His shitful piece of Code,
is Especially Important, ant that in his case O_DIRECT
is perfectly suitable. And in the case His code is
someway performance critical, then most likely O_DIRECT
will really improve his Code benchmarks, and that is
making things really awful, leading to the hell large
crowd of pig happy dudes thinking their useless code
is life critical, and thus dooming linux.
Maybe i`m stupid, as these potential dudes, and
painting things in too dark colors, but O_DIRECT,
i think, is a dangerous thing to play with.
That is why, i think, Linus as far as i can properly
recall, wasn`t happy with it et al.
Maybe i`m missing the whole point, and thus i want to
hear what other people will tell about it.
Cheers,
Samium Gromoff
next reply other threads:[~2001-07-03 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 20:34 Samium Gromoff [this message]
2001-07-03 20:38 ` kernel
2001-07-03 21:12 ` Anton Altaparmakov
2001-07-04 17:52 ` Stephen C. Tweedie
2001-07-04 18:27 ` Miquel van Smoorenburg
2001-07-04 18:34 ` Stephen C. Tweedie
2001-07-04 20:23 ` Miquel van Smoorenburg
2001-07-05 15:06 ` Stephen C. Tweedie
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=E15HWsV-0000lM-00@f12.port.ru \
--to=_deepfire@mail.ru \
--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®