All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>,
	axboe@kernel.dk, Milosz Tanski <milosz@adfin.com>,
	Goldwyn Rodrigues <rgoldwyn@suse.com>,
	mgorman@suse.de, Volker.Lendecke@sernet.de,
	linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: non-blockling buffered reads
Date: Fri, 30 Jun 2017 02:34:57 +0200	[thread overview]
Message-ID: <20170630003457.GA5369@lst.de> (raw)
In-Reply-To: <20170629234657.GO10672@ZenIV.linux.org.uk>

On Fri, Jun 30, 2017 at 12:46:57AM +0100, Al Viro wrote:
> Hmm...  It's not quite non-blocking, though - copy_page_to_iter() can
> bloody well block, as any copying to userland.  I'm not saying that
> it's a significant problem (if you are reading into something that
> had been mmaped from NFS server, etc., you are getting what you'd
> asked for), but it's worth documenting.

True.  I'll ensure this is documented in the man page.

  reply	other threads:[~2017-06-30  0:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 21:25 non-blockling buffered reads Christoph Hellwig
2017-06-29 21:25 ` [PATCH 1/3] fs: pass iocb to do_generic_file_read Christoph Hellwig
2017-06-29 21:25 ` [PATCH 2/3] fs: support IOCB_NOWAIT in generic_file_buffered_read Christoph Hellwig
2017-06-29 21:25 ` [PATCH 3/3] fs: support RWF_NOWAIT for buffered reads Christoph Hellwig
2017-06-30  3:43   ` Goldwyn Rodrigues
2017-06-29 23:46 ` non-blockling " Al Viro
2017-06-30  0:34   ` Christoph Hellwig [this message]
2017-06-30  1:11 ` Milosz Tanski
2017-06-30  1:12 ` Milosz Tanski

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=20170630003457.GA5369@lst.de \
    --to=hch@lst.de \
    --cc=Volker.Lendecke@sernet.de \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=milosz@adfin.com \
    --cc=rgoldwyn@suse.com \
    --cc=viro@ZenIV.linux.org.uk \
    /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.