Util-Linux package development
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH v1 0/2] losetup: support direct-IO to backing file
Date: Thu, 19 Nov 2015 12:04:11 +0100	[thread overview]
Message-ID: <20151119110411.GA4955@ws.net.home> (raw)
In-Reply-To: <1447770768-15358-1-git-send-email-tom.leiming@gmail.com>

On Tue, Nov 17, 2015 at 10:32:46PM +0800, Ming Lei wrote:
>  include/loopdev.h   |  4 ++++
>  lib/loopdev.c       | 40 ++++++++++++++++++++++++++++++++++++++++
>  sys-utils/losetup.c | 33 +++++++++++++++++++++++++++++++--
>  3 files changed, 75 insertions(+), 2 deletions(-)
> 
> 
> [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bc07c10a3603a5ab3ef01ba42b3d41f9ac63d1b6
> 
> V1:
> 	- support to set direct IO for 'new' device, such as 
> 		loseutp --direct-io 1 -f test.img

Applied, thanks!

I have a little bit changed the command line option to:

    --direct-io[=on|off]

where the default is "on", so you can use:

    losetup -f --direct-io file.img

to enable direct-io, to disable you have to use:

    losetup --direct-io=off /dev/loop0

I guess the most common usage will be to enable direct I/O :-)


https://github.com/karelzak/util-linux/commit/f98d9641a371421640a8f1cfe497030758f86dca

    Karel


-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

      parent reply	other threads:[~2015-11-19 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17 14:32 [PATCH v1 0/2] losetup: support direct-IO to backing file Ming Lei
2015-11-17 14:32 ` [PATCH v1 1/2] losetup: support ioctl cmd of LOOP_SET_DIRECT_IO Ming Lei
2015-11-17 14:32 ` [PATCH v1 2/2] losetup: support list direct io Ming Lei
2015-11-19 11:04 ` Karel Zak [this message]

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=20151119110411.GA4955@ws.net.home \
    --to=kzak@redhat.com \
    --cc=tom.leiming@gmail.com \
    --cc=util-linux@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