From: Bodo Stroesser <bostroesser@gmail.com>
To: Douglas Gilbert <dgilbert@interlog.com>,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: martin.petersen@oracle.com, axboe@kernel.dk, bvanassche@acm.org
Subject: Re: [PATCH v3 2/4] scatterlist: add sgl_copy_sgl() function
Date: Tue, 3 Nov 2020 14:26:10 +0100 [thread overview]
Message-ID: <1a7b2ffc-b289-f650-576f-fac832fa0489@gmail.com> (raw)
In-Reply-To: <20201019191928.77845-3-dgilbert@interlog.com>
Am 19.10.20 um 21:19 schrieb Douglas Gilbert:
> Both the SCSI and NVMe subsystems receive user data from the block
> layer in scatterlist_s (aka scatter gather lists (sgl) which are
> often arrays). If drivers in those subsystems represent storage
> (e.g. a ramdisk) or cache "hot" user data then they may also
> choose to use scatterlist_s. Currently there are no sgl to sgl
> operations in the kernel. Start with a sgl to sgl copy. Stops
> when the first of the number of requested bytes to copy, or the
> source sgl, or the destination sgl is exhausted. So the
> destination sgl will _not_ grow.
>
> Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>
> ---
> include/linux/scatterlist.h | 4 ++
> lib/scatterlist.c | 75 +++++++++++++++++++++++++++++++++++++
> 2 files changed, 79 insertions(+)
>
> diff --git a/include/linux/scatterlist.h b/include/linux/scatterlist.h
> index 80178afc2a4a..6649414c0749 100644
> --- a/include/linux/scatterlist.h
> +++ b/include/linux/scatterlist.h
> @@ -321,6 +321,10 @@ size_t sg_pcopy_to_buffer(struct scatterlist *sgl, unsigned int nents,
> size_t sg_zero_buffer(struct scatterlist *sgl, unsigned int nents,
> size_t buflen, off_t skip);
>
> +size_t sgl_copy_sgl(struct scatterlist *d_sgl, unsigned int d_nents, off_t d_skip,
> + struct scatterlist *s_sgl, unsigned int s_nents, off_t s_skip,
> + size_t n_bytes);
> +
> /*
> * Maximum number of entries that will be allocated in one piece, if
> * a list larger than this is required then chaining will be utilized.
> diff --git a/lib/scatterlist.c b/lib/scatterlist.c
> index d5770e7f1030..1f9e093ad7da 100644
> --- a/lib/scatterlist.c
> +++ b/lib/scatterlist.c
> @@ -974,3 +974,78 @@ size_t sg_zero_buffer(struct scatterlist *sgl, unsigned int nents,
> return offset;
> }
> EXPORT_SYMBOL(sg_zero_buffer);
> +
> +/**
> + * sgl_copy_sgl - Copy over a destination sgl from a source sgl
> + * @d_sgl: Destination sgl
> + * @d_nents: Number of SG entries in destination sgl
> + * @d_skip: Number of bytes to skip in destination before starting
> + * @s_sgl: Source sgl
> + * @s_nents: Number of SG entries in source sgl
> + * @s_skip: Number of bytes to skip in source before starting
> + * @n_bytes: The (maximum) number of bytes to copy
> + *
> + * Returns:
> + * The number of copied bytes.
> + *
> + * Notes:
> + * Destination arguments appear before the source arguments, as with memcpy().
> + *
> + * Stops copying if either d_sgl, s_sgl or n_bytes is exhausted.
> + *
> + * Since memcpy() is used, overlapping copies (where d_sgl and s_sgl belong
> + * to the same sgl and the copy regions overlap) are not supported.
> + *
> + * Large copies are broken into copy segments whose sizes may vary. Those
> + * copy segment sizes are chosen by the min3() statement in the code below.
> + * Since SG_MITER_ATOMIC is used for both sides, each copy segment is started
> + * with kmap_atomic() [in sg_miter_next()] and completed with kunmap_atomic()
> + * [in sg_miter_stop()]. This means pre-emption is inhibited for relatively
> + * short periods even in very large copies.
> + *
> + * If d_skip is large, potentially spanning multiple d_nents then some
> + * integer arithmetic to adjust d_sgl may improve performance. For example
> + * if d_sgl is built using sgl_alloc_order(chainable=false) then the sgl
> + * will be an array with equally sized segments facilitating that
> + * arithmetic. The suggestion applies to s_skip, s_sgl and s_nents as well.
> + *
> + **/
> +size_t sgl_copy_sgl(struct scatterlist *d_sgl, unsigned int d_nents, off_t d_skip,
> + struct scatterlist *s_sgl, unsigned int s_nents, off_t s_skip,
> + size_t n_bytes)
> +{
> + size_t len;
> + size_t offset = 0;
> + struct sg_mapping_iter d_iter, s_iter;
> +
> + if (n_bytes == 0)
> + return 0;
> + sg_miter_start(&s_iter, s_sgl, s_nents, SG_MITER_ATOMIC | SG_MITER_FROM_SG);
> + sg_miter_start(&d_iter, d_sgl, d_nents, SG_MITER_ATOMIC | SG_MITER_TO_SG);
> + if (!sg_miter_skip(&s_iter, s_skip))
> + goto fini;
> + if (!sg_miter_skip(&d_iter, d_skip))
> + goto fini;
> +
> + while (offset < n_bytes) {
> + if (!sg_miter_next(&s_iter))
> + break;
> + if (!sg_miter_next(&d_iter))
> + break;
> + len = min3(d_iter.length, s_iter.length, n_bytes - offset);
> +
> + memcpy(d_iter.addr, s_iter.addr, len);
> + offset += len;
> + /* LIFO order (stop d_iter before s_iter) needed with SG_MITER_ATOMIC */
> + d_iter.consumed = len;
> + sg_miter_stop(&d_iter);
> + s_iter.consumed = len;
> + sg_miter_stop(&s_iter);
> + }
> +fini:
> + sg_miter_stop(&d_iter);
> + sg_miter_stop(&s_iter);
> + return offset;
> +}
> +EXPORT_SYMBOL(sgl_copy_sgl);
> +
>
Second try, this time with correct tag.
Reviewed-by: Bodo Stroesser <bostroesser@gmail.com>
next prev parent reply other threads:[~2020-11-03 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 19:19 [PATCH v3 0/4] scatterlist: add new capabilities Douglas Gilbert
2020-10-19 19:19 ` [PATCH v3 1/4] sgl_alloc_order: remove 4 GiB limit, sgl_free() warning Douglas Gilbert
2020-11-03 12:54 ` Bodo Stroesser
2020-11-04 18:26 ` Douglas Gilbert
2020-10-19 19:19 ` [PATCH v3 2/4] scatterlist: add sgl_copy_sgl() function Douglas Gilbert
2020-11-03 13:22 ` Bodo Stroesser
2020-11-03 13:26 ` Bodo Stroesser [this message]
2020-10-19 19:19 ` [PATCH v3 3/4] scatterlist: add sgl_compare_sgl() function Douglas Gilbert
2020-11-03 13:24 ` Bodo Stroesser
2020-10-19 19:19 ` [PATCH v3 4/4] scatterlist: add sgl_memset() Douglas Gilbert
2020-11-03 13:28 ` Bodo Stroesser
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=1a7b2ffc-b289-f650-576f-fac832fa0489@gmail.com \
--to=bostroesser@gmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dgilbert@interlog.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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
all inboxes | Powered by JetHome®