From: David Laight <David.Laight@ACULAB.COM>
To: 'David Howells' <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@list.de>,
"Christian Brauner" <christian@brauner.io>,
Matthew Wilcox <willy@infradead.org>,
"Jeff Layton" <jlayton@kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v3 2/2] iov_iter: Don't deal with iter->copy_mc in memcpy_from_iter_mc()
Date: Wed, 16 Aug 2023 12:28:47 +0000 [thread overview]
Message-ID: <03730b50cebb4a349ad8667373bb8127@AcuMS.aculab.com> (raw)
In-Reply-To: <20230816120741.534415-3-dhowells@redhat.com>
From: David Howells
> Sent: Wednesday, August 16, 2023 1:08 PM
Given:
> iter->copy_mc is only used with a bvec iterator and only by
> dump_emit_page() in fs/coredump.c so rather than handle this in
> memcpy_from_iter_mc() where it is checked repeatedly by _copy_from_iter() and
> copy_page_from_iter_atomic(),
Instead of adding the extra check to every copy:
> +static __always_inline
> +size_t __copy_from_iter(void *addr, size_t bytes, struct iov_iter *i)
> +{
> + if (unlikely(iov_iter_is_copy_mc(i)))
> + return __copy_from_iter_mc(addr, bytes, i);
> + return iterate_and_advance(i, bytes, addr,
> + copy_from_user_iter, memcpy_from_iter);
> }
Couldn't the relevant code directly call __copy_frtom_iter_mc() ?
Or a version then checked iov_is_copy_mc() and then fell
back to the standard function.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2023-08-16 12:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 12:07 [PATCH v3 0/2] iov_iter: Convert the iterator macros into inline funcs David Howells
2023-08-16 12:07 ` [PATCH v3 1/2] iov_iter: Convert iterate*() to " David Howells
2023-08-16 12:07 ` [PATCH v3 2/2] iov_iter: Don't deal with iter->copy_mc in memcpy_from_iter_mc() David Howells
2023-08-16 12:28 ` David Laight [this message]
2023-08-16 13:00 ` David Howells
2023-08-16 14:19 ` David Laight
2023-08-16 18:50 ` Linus Torvalds
2023-08-16 20:35 ` David Howells
2023-08-17 4:18 ` Linus Torvalds
2023-08-17 8:41 ` David Laight
2023-08-17 14:38 ` Linus Torvalds
2023-08-17 15:16 ` David Laight
2023-08-17 15:31 ` Linus Torvalds
2023-08-17 16:06 ` David Laight
2023-08-18 15:19 ` David Howells
2023-08-18 15:42 ` David Laight
2023-08-18 16:48 ` David Howells
2023-08-18 21:39 ` David Laight
2023-08-18 11:42 ` David Howells
2023-08-18 12:16 ` David Laight
2023-08-18 12:26 ` Matthew Wilcox
2023-08-18 12:41 ` David Laight
2023-08-18 13:33 ` David Howells
2023-08-18 11:39 ` David Howells
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=03730b50cebb4a349ad8667373bb8127@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=axboe@kernel.dk \
--cc=christian@brauner.io \
--cc=dhowells@redhat.com \
--cc=hch@list.de \
--cc=jlayton@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).