mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@gmx.de>
To: Jonathan Corbet <corbet@lwn.net>,
	Michael Tokarev <mjt@tls.msk.ru>,
	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:49:27 +0100	[thread overview]
Message-ID: <E1LnLnk-0002B1-5Y@be1.7eggert.dyndns.org> (raw)
In-Reply-To: <cks6g-7wu-13@gated-at.bofh.it>

Jonathan Corbet <corbet@lwn.net> wrote:
> Michael Tokarev <mjt@tls.msk.ru> wrote:

>> 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?

As long as you don't fix all the legacy applications to use O_DIRECT.

> This was discussed a while back.  My understanding is that there are
> people using it.  It is a user-space ABI of sorts which can't just be
> yanked arbitrarily.  The right thing to do is probably to replace it
> with a shell implementation that just opens the device using O_DIRECT,
> but nobody has actually done that...

It had long been done when before it was discussed the last time.


       reply	other threads:[~2009-03-27 23:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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

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=E1LnLnk-0002B1-5Y@be1.7eggert.dyndns.org \
    --to=7eggert@gmx.de \
    --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®