From: Andi Kleen <ak@suse.de>
To: Dan Kegel <dank@kegel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: O_DIRECT please; Sybase 12.5
Date: 29 Jun 2001 12:42:37 +0200 [thread overview]
Message-ID: <oupwv5v36ua.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <3B3C4CB4.6B3D2B2F@kegel.com.suse.lists.linux.kernel>
In-Reply-To: Dan Kegel's message of "29 Jun 2001 11:38:26 +0200"
Dan Kegel <dank@kegel.com> writes:
>
> 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
When Sybase always submits its buffers block aligned (same requirement as
for raw io) you can do it with a simple LD_PRELOAD hack.
I hacked sapdb (which has source available unlike sybase) to do direct IO
and it seems to not hurt at least.
> 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 :-(
LVM makes raw partitions much less worse than they used to be. It is
basically a file system of raw partitions; allowing you to move and resize
them.
-Andi
next parent reply other threads:[~2001-06-29 10:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B3C4CB4.6B3D2B2F@kegel.com.suse.lists.linux.kernel>
2001-06-29 10:42 ` Andi Kleen [this message]
2001-06-29 9:39 O_DIRECT please; Sybase 12.5 Dan Kegel
2001-06-29 9:50 ` 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
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=oupwv5v36ua.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=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