From: Dan Kegel <dank@kegel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: O_DIRECT please; Sybase 12.5
Date: Fri, 29 Jun 2001 02:39:00 -0700 [thread overview]
Message-ID: <3B3C4CB4.6B3D2B2F@kegel.com> (raw)
At work I had to sit through a meeting where I heard
the boss say "If Linux makes Sybase go through the page cache on
reads, maybe we'll just have to switch to Solaris. That's
a serious performance problem."
All I could say was "I expect Linux will support O_DIRECT
soon, and Sybase will support that within a year."
Er, so did I promise too much? Andrea mentioned O_DIRECT recently
( http://marc.theaimsgroup.com/?l=linux-kernel&m=99253913516599&w=2,
http://lwn.net/2001/0510/bigpage.php3 )
Is it supported yet in 2.4, or is this a 2.5 thing?
And what are the chances Sybase will support that flag any time
soon? I just read on news://forums.sybase.com/sybase.public.ase.linux
that Sybase ASE 12.5 was released today, and a 60 day eval is downloadable
for NT and Linux. I'm downloading now; it's a biggie.
It supports raw partitions, which is good; that might satisfy my
boss (although the administration will be a pain, and I'm not
sure whether it's really supported by Dell RAID devices).
I'd prefer O_DIRECT :-(
Hope somebody can give me encouraging news.
Thanks,
Dan
next reply other threads:[~2001-06-29 9:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 9:39 Dan Kegel [this message]
2001-06-29 9:50 ` O_DIRECT please; Sybase 12.5 Alan Cox
2001-06-29 10:16 ` Dan Kegel
2001-06-29 12:49 ` Mike Harrold
2001-07-05 13:59 ` Andrea Arcangeli
2001-06-29 15:23 ` Steve Lord
2001-07-03 9:42 ` Stephen C. Tweedie
2001-07-03 15:10 ` Daryll Strauss
2001-07-03 15:48 ` Stephen C. Tweedie
2001-07-05 13:53 ` Andrea Arcangeli
2001-07-05 14:28 ` Andrew Morton
2001-07-05 14:37 ` Andrea Arcangeli
2001-07-05 15:06 ` Andrew Morton
2001-07-06 0:25 ` Keith Owens
[not found] <3B3C4CB4.6B3D2B2F@kegel.com.suse.lists.linux.kernel>
2001-06-29 10:42 ` Andi Kleen
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=3B3C4CB4.6B3D2B2F@kegel.com \
--to=dank@kegel.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;
as well as URLs for NNTP newsgroup(s).