From: Greg KH <gregkh@linuxfoundation.org>
To: Qingsong Chen <changxian.cqs@antgroup.com>
Cc: linux-kernel@vger.kernel.org, 田洪亮 <tate.thl@antgroup.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Rust scatterlist abstractions
Date: Mon, 12 Jun 2023 07:38:27 +0200 [thread overview]
Message-ID: <2023061257-unbeaten-dropkick-a25c@gregkh> (raw)
In-Reply-To: <37513fcd-b371-cc2f-b7f9-e94b045d8c5c@antgroup.com>
On Mon, Jun 12, 2023 at 11:49:51AM +0800, Qingsong Chen wrote:
> On 6/10/23 11:35 PM, Greg KH wrote:
> > On Sat, Jun 10, 2023 at 05:33:47PM +0200, Greg KH wrote:
> > > On Sat, Jun 10, 2023 at 06:49:06PM +0800, Qingsong Chen wrote:
> > > > Hi All!
> > > >
> > > > This is a version of scatterlist abstractions for Rust drivers.
> > > >
> > > > Scatterlist is used for efficient management of memory buffers, which is
> > > > essential for many kernel-level operations such as Direct Memory Access
> > > > (DMA) transfers and crypto APIs.
> > > >
> > > > This patch should be a good start to introduce the crypto APIs for Rust
> > > > drivers and to develop cipher algorithms in Rust later.
> > >
> > > I thought we were getting rid of the scatter list api for the crypto
> > > drivers, so this shouldn't be needed going forward, right? Why not just
> > > use the direct apis instead?
> >
> > See https://lore.kernel.org/r/ZH2hgrV6po9dkxi+@gondor.apana.org.au for
> > the details of that (sorry I forgot the link first time...)
>
> Thanks for the information. I agree that turning simple buffers into
> sg-bufs is not a good idea. If I were implementing a new cipher
> algorithm, I would definitely follow the `struct cipher_alg`, which
> takes simple `u8 *` pointer as parameter. However, if we'd like to
> utilize some existing ciphers, such as aead, we still need scatterlists
> to construct an `aead_request` for further operations, util changes are
> made to the underlying interface.
Why not make the changes to the C code first, and get those changes
merged, making this patch series not needed at all?
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-12 5:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 10:49 [PATCH v3 0/3] Rust scatterlist abstractions Qingsong Chen
2023-06-10 10:49 ` [PATCH v3 1/3] rust: kernel: add ScatterList abstraction Qingsong Chen
2023-06-12 15:08 ` Martin Rodriguez Reboredo
2023-06-10 10:49 ` [PATCH v3 2/3] rust: kernel: implement iterators for ScatterList Qingsong Chen
2023-06-12 15:10 ` Martin Rodriguez Reboredo
2023-06-10 10:49 ` [PATCH v3 3/3] rust: kernel: add SgTable abstraction Qingsong Chen
2023-06-12 16:13 ` Martin Rodriguez Reboredo
2023-06-10 15:33 ` [PATCH v3 0/3] Rust scatterlist abstractions Greg KH
2023-06-10 15:35 ` Greg KH
2023-06-12 3:49 ` Qingsong Chen
2023-06-12 5:38 ` Greg KH [this message]
2023-06-12 7:03 ` Qingsong Chen
2023-06-12 7:12 ` Greg KH
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=2023061257-unbeaten-dropkick-a25c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alex.gaynor@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=changxian.cqs@antgroup.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tate.thl@antgroup.com \
--cc=wedsonaf@gmail.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;
as well as URLs for NNTP newsgroup(s).