From: Christoph Hellwig <hch@lst.de>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Christoph Hellwig <hch@lst.de>,
arnd@arndb.de, gregkh@linuxfoundation.org,
christophe.leroy@csgroup.eu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] /dev/zero: also implement ->read
Date: Mon, 7 Sep 2020 08:20:26 +0200 [thread overview]
Message-ID: <20200907062026.GA19076@lst.de> (raw)
In-Reply-To: <8d430999-b155-dbfa-e7db-f414b48014b1@rasmusvillemoes.dk>
On Mon, Sep 07, 2020 at 12:34:37AM +0200, Rasmus Villemoes wrote:
> On 03/09/2020 17.59, Christoph Hellwig wrote:
> > Christophe reported a major speedup due to avoiding the iov_iter
> > overhead, so just add this trivial function. Note that /dev/zero
> > already implements both an iter and non-iter writes so this just
> > makes it more symmetric.
> >
> > Christophe Leroy <christophe.leroy@csgroup.eu>
>
> ?-by ?
Suggested-by,
> > +static ssize_t read_zero(struct file *file, char __user *buf,
> > + size_t count, loff_t *ppos)
> > +{
> > + size_t cleared = 0;
> > +
> > + while (count) {
> > + size_t chunk = min_t(size_t, count, PAGE_SIZE);
> > +
> > + if (clear_user(buf + cleared, chunk))
> > + return cleared ? cleared : -EFAULT;
>
> Probably nobody really cares, but currently doing
>
> read(fd, &unmapped_page - 5, 123);
>
> returns 5, and those five bytes do get cleared; if I'm reading the above
> right you'd return -EFAULT for that case.
>
>
> > + cleared += chunk;
> > + count -= chunk;
> > +
> > + if (signal_pending(current))
> > + return cleared ? cleared : -ERESTARTSYS;
>
> I can't see how we can get here without 'cleared' being positive, so
> this can just be 'return cleared' (and if you fix the above EFAULT case
> to more accurately track how much got cleared, there's probably no
> longer any code to be symmetric with anyway).
Yeah, I'll fix these up and resend.
next prev parent reply other threads:[~2020-09-07 6:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 15:59 [PATCH] /dev/zero: also implement ->read Christoph Hellwig
2020-09-03 16:05 ` Christophe Leroy
2020-09-03 21:35 ` David Laight
2020-09-06 18:21 ` Pavel Machek
2020-09-06 18:35 ` Christophe Leroy
2020-09-06 18:38 ` Pavel Machek
2020-09-06 18:47 ` Christophe Leroy
2020-09-06 20:09 ` gregkh
2020-09-06 20:52 ` David Laight
2020-09-07 4:44 ` Christophe Leroy
2020-09-07 8:18 ` David Laight
2020-09-03 17:51 ` Christophe Leroy
2020-09-03 18:02 ` Greg KH
2020-09-06 22:34 ` Rasmus Villemoes
2020-09-07 6:20 ` Christoph Hellwig [this message]
2020-09-07 6:50 ` Rasmus Villemoes
2020-09-07 7:30 ` Christoph Hellwig
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=20200907062026.GA19076@lst.de \
--to=hch@lst.de \
--cc=arnd@arndb.de \
--cc=christophe.leroy@csgroup.eu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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