From: Lee Revell <rlrevell@joe-job.com>
To: gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] the scheduled removal of the obsolete raw driver
Date: Sat, 21 Jan 2006 19:15:45 -0500 [thread overview]
Message-ID: <1137888945.11722.5.camel@mindpipe> (raw)
In-Reply-To: <200601211909.15559.gene.heskett@verizon.net>
On Sat, 2006-01-21 at 19:09 -0500, Gene Heskett wrote:
> On Saturday 21 January 2006 18:59, Doug McNaught wrote:
> >Gene Heskett <gene.heskett@verizon.net> writes:
> >>>No, it's a different raw driver, for big databases that basically
> >>> want their own custom filesystem on a disk.
> >>
> >> With the attendent possibility of rendering the whole thing
> >> unrecoverably moot?
> >>
> >> OTOH, if this database actually does have a better way, and its
> >> mature and proven, then I see no reason to cripple the database
> >> people just to remove what is viewed as a potentially dangerous path
> >> to the media surface for the unwashed to abuse.
> >
> >The database people have a newer and supported way to do that, via the
> >O_DIRECT flag to open(). They aren't losing any functionality.
> >
> Good, but what about speed, is that impacted in any way they can
> measure, or is this flag/method actually faster than the raw driver is?
A loss of speed is a loss of functionality, and would not be accepted.
Lee
next prev parent reply other threads:[~2006-01-22 0:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 3:02 [2.6 patch] the scheduled removal of the obsolete raw driver Adrian Bunk
2006-01-19 3:41 ` Andrew Morton
2006-01-19 5:43 ` Chen, Kenneth W
2006-01-21 1:02 ` Adrian Bunk
2006-01-21 1:08 ` Chen, Kenneth W
2006-01-21 1:49 ` Alan Cox
2006-01-19 16:10 ` Adrian Bunk
2006-01-19 16:44 ` Badari Pulavarty
2006-01-19 16:52 ` Mark Lord
2006-01-19 16:58 ` Adrian Bunk
2006-01-19 18:14 ` Badari Pulavarty
2006-01-20 8:24 ` [SARCASM] " Ingo Oeser
2006-01-20 14:02 ` Jan Engelhardt
2006-01-22 12:51 ` [OT] " Alexander E. Patrakov
2006-01-21 8:52 ` Arjan van de Ven
2006-01-21 19:41 ` Dave Jones
2006-01-21 21:17 ` Andrew Morton
2006-01-21 21:25 ` Arjan van de Ven
2006-01-21 21:35 ` Andrew Morton
2006-01-21 21:50 ` Arjan van de Ven
2006-01-22 17:50 ` Jesper Juhl
2006-01-21 23:26 ` Gene Heskett
2006-01-21 23:30 ` Lee Revell
2006-01-21 23:53 ` Gene Heskett
2006-01-21 23:59 ` Doug McNaught
2006-01-22 0:09 ` Gene Heskett
2006-01-22 0:15 ` Lee Revell [this message]
2006-01-22 1:30 ` Doug McNaught
2006-01-22 8:14 ` Arjan van de Ven
2006-01-22 20:33 ` Alan Cox
2006-01-22 21:53 ` Jan Engelhardt
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=1137888945.11722.5.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=gene.heskett@verizon.net \
--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