Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3;
From:   David Howells <dhowells@redhat.com>
To:     Al Viro <viro@zeniv.linux.org.uk>,
        Linus Torvalds <torvalds@linux-foundation.org>
Cc:     David Howells <dhowells@redhat.com>, Jens Axboe <axboe@kernel.dk>,
        Christoph Hellwig <hch@lst.de>,
        Christian Brauner <christian@brauner.io>,
        David Laight <David.Laight@ACULAB.COM>,
        Matthew Wilcox <willy@infradead.org>,
        Brendan Higgins <brendanhiggins@google.com>,
        David Gow <davidgow@google.com>, linux-fsdevel@vger.kernel.org,
        linux-block@vger.kernel.org, linux-mm@kvack.org,
        netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
        kunit-dev@googlegroups.com, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/9] iov_iter: kunit: Cleanup, abstraction and more tests
Date:   Thu, 14 Sep 2023 23:15:17 +0100
Message-ID: <20230914221526.3153402-1-dhowells@redhat.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi Al, Linus,

These patches make some changes to the kunit tests previously added for
iov_iter testing, in particular adding support for testing UBUF/IOVEC
iterators:

 (1) Clean up a couple of checkpatch style complaints.

 (2) Consolidate some repeated bits of code into helper functions and use
     the same struct to represent straight offset/address ranges and
     partial page lists.

 (3) Add a function to set up a userspace VM, attach the VM to the kunit
     testing thread, create an anonymous file, stuff some pages into the
     file and map the file into the VM to act as a buffer that can be used
     with UBUF/IOVEC iterators.

     I map an anonymous file with pages attached rather than using MAP_ANON
     so that I can check the pages obtained from iov_iter_extract_pages()
     without worrying about them changing due to swap, migrate, etc..

     [?] Is this the best way to do things?  Mirroring execve, it requires
     a number of extra core symbols to be exported.  Should this be done in
     the core code?

 (4) Add tests for copying into and out of UBUF and IOVEC iterators.

 (5) Add tests for extracting pages from UBUF and IOVEC iterators.

 (6) Add tests to benchmark copying 256MiB to UBUF, IOVEC, KVEC, BVEC and
     XARRAY iterators.

     [!] Note that this requires 256MiB of memory for UBUF and IOVEC; the
     KVEC, BVEC and XARRAY benchmarking maps a single page multiple times.
     I might be able to shrink that if I can add the same page multiple
     times to the anon file's pagecache.  I'm sure this is not recommended,
     but I might be able to get away with it for this particular
     application.

 (7) Add a test to benchmark copying 256MiB through dynamically allocated
     256-page bvecs to simulate bio construction.

Example benchmarks output:

 iov_kunit_benchmark_ubuf: avg 26899 uS, stddev 142 uS
 iov_kunit_benchmark_iovec: avg 26897 uS, stddev 74 uS
 iov_kunit_benchmark_kvec: avg 2688 uS, stddev 35 uS
 iov_kunit_benchmark_bvec: avg 3139 uS, stddev 21 uS
 iov_kunit_benchmark_bvec_split: avg 3379 uS, stddev 15 uS
 iov_kunit_benchmark_xarray: avg 3582 uS, stddev 13 uS

I've pushed the patches here also:

	https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=iov-kunit

David

David Howells (9):
  iov_iter: Fix some checkpatch complaints in kunit tests
  iov_iter: Consolidate some of the repeated code into helpers
  iov_iter: Consolidate the test vector struct in the kunit tests
  iov_iter: Consolidate bvec pattern checking
  iov_iter: Create a function to prepare userspace VM for UBUF/IOVEC
    tests
  iov_iter: Add copy kunit tests for ITER_UBUF and ITER_IOVEC
  iov_iter: Add extract kunit tests for ITER_UBUF and ITER_IOVEC
  iov_iter: Add benchmarking kunit tests
  iov_iter: Add benchmarking kunit tests for UBUF/IOVEC

 fs/anon_inodes.c     |    1 +
 kernel/fork.c        |    2 +
 lib/kunit_iov_iter.c | 1211 +++++++++++++++++++++++++++++++++++-------
 mm/mmap.c            |    1 +
 mm/util.c            |    1 +
 5 files changed, 1024 insertions(+), 192 deletions(-)