mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Dan Carpenter <error27@gmail.com>,
	linux-kernel@vger.kernel.org, eteo@redhat.com
Subject: Re: [patch] char/raw.c locking on error
Date: Sat, 28 Mar 2009 00:23:29 +0000	[thread overview]
Message-ID: <20090328002329.25730798@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <49CD46C8.8040606@msgid.tls.msk.ru>

On Sat, 28 Mar 2009 00:36:08 +0300
Michael Tokarev <mjt@tls.msk.ru> wrote:

> Jonathan Corbet wrote:
> > (I bet raw doesn't need BKL at all; I'll see if I can't find some time
> > to have a look later on).
> 
> Is it still in use - the raw driver, that is?  Nowadays,
> every block device can be opened in direct mode by using
> O_DIRECT - this is what raw does.  I mean, is it worth
> spending even more time on it?

Certainly when I worked for a vendor there were some big proprietary
applications using the raw interface both because it was an established
API and also because it mirrorred various Unixen and relatives they also
ran the apps on with the same basic code.

Attempts to kill it were met with pretty forceful objections.


  parent reply	other threads:[~2009-03-28  0:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 10:28 Dan Carpenter
2009-03-27 15:48 ` Jonathan Corbet
2009-03-27 21:36   ` Michael Tokarev
2009-03-27 21:44     ` Jonathan Corbet
2009-03-28  0:23     ` Alan Cox [this message]
     [not found] <ckhDP-7Ey-1@gated-at.bofh.it>
     [not found] ` <ckmtX-6ZA-25@gated-at.bofh.it>
     [not found]   ` <ckrWP-7iQ-33@gated-at.bofh.it>
     [not found]     ` <cks6g-7wu-13@gated-at.bofh.it>
2009-03-27 23:49       ` Bodo Eggert

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=20090328002329.25730798@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=corbet@lwn.net \
    --cc=error27@gmail.com \
    --cc=eteo@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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®