All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M. Warner Losh" <imp@bsdimp.com>
To: hch@lst.de
Cc: nolan@sigbus.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] block/raw-posix.c:hdev_create() on FreeBSD and in general
Date: Wed, 20 May 2009 08:41:24 -0600 (MDT)	[thread overview]
Message-ID: <20090520.084124.1715680382.imp@bsdimp.com> (raw)
In-Reply-To: <20090520080723.GA2957@lst.de>

In message: <20090520080723.GA2957@lst.de>
            Christoph Hellwig <hch@lst.de> writes:
: Didn't FreeBSD do away with block device nodes in the 4.x release cycle?

Yes.  Block devices are a quaint relic of the past, and aren't
needed. :)

: In that case we will never allow to create host devices on FreeBSD
: with this code.

Yes, on FreeBSD, just use the char dev.

: Also I think we should allow creating the host devices on all supported
: operating systems.  For Linux we should use block devices, for FreeBSD
: always char devices.  For the other BSDs and Solaris do we allow only
: block or also the raw char devices?  Not sure if they actually support
: O_DIRECT for block devices nodes which pretty much is a Linux-ism so
: for cache=none at least we should probably open the raw nodes..

Other BSDs still have block devices.  O_DIRECT is supported in at
least NetBSD (and FreeBSD).

Warner

  reply	other threads:[~2009-05-20 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  8:07 [Qemu-devel] block/raw-posix.c:hdev_create() on FreeBSD and in general Christoph Hellwig
2009-05-20 14:41 ` M. Warner Losh [this message]
2009-05-20 15:03   ` Christoph Hellwig
2009-05-20 16:24     ` M. Warner Losh

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=20090520.084124.1715680382.imp@bsdimp.com \
    --to=imp@bsdimp.com \
    --cc=hch@lst.de \
    --cc=nolan@sigbus.net \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.