From: Jiri Slaby <jirislaby@kernel.org>
To: stefani@seibold.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] kfifo: small cleanup + linear and skip helpers
Date: Fri, 23 Feb 2024 13:08:13 +0100 [thread overview]
Message-ID: <53095fb1-1093-4db0-8c8b-ef3d7d673628@kernel.org> (raw)
In-Reply-To: <20240223115155.8806-1-jirislaby@kernel.org>
On 23. 02. 24, 12:51, Jiri Slaby (SUSE) wrote:
> Hi,
>
> this is a small cleanup of kfifo.
>
> More importantly, it introduces three helpers: kfifo_skip_count(),
> kfifo_out_linear() and kfifo_out_linear_ptr(). They allow using kfifo in
> the serial layer.
>
> They are needed as up to now, there is no way to "peek" the data without
> actually copying to a temporary buffer. kfifo_out_linear*() allow that
> and kfifo_skip_count() then allows for tail moving after the copy is
> done. Note the copy is usually performed directly to hardware e.g. via
> outb(), hence the need for peek without copying anywhere.
Sorry, this reasoning is bogus. outb() would be using kfifo_out(), of
course.
The requirement comes from (for example):
* memcpy_toio() in neo_copy_data_from_queue_to_uart(),
* regmap_noinc_write() in max310x_handle_tx()),
* and similar.
The kfifo data are there directly copied to HW in a batch, without the
need of temp buffers.
thanks,
--
js
suse labs
prev parent reply other threads:[~2024-02-23 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 11:51 Jiri Slaby (SUSE)
2024-02-23 11:51 ` [PATCH 1/4] kfifo: drop __kfifo_dma_out_finish_r() Jiri Slaby (SUSE)
2024-02-24 0:27 ` Andrew Morton
2024-02-23 11:51 ` [PATCH 2/4] kfifo: introduce and use kfifo_skip_count() Jiri Slaby (SUSE)
2024-02-23 11:51 ` [PATCH 3/4] kfifo: add kfifo_out_linear{,_ptr}() Jiri Slaby (SUSE)
2024-02-24 2:31 ` Andrew Morton
2024-02-26 5:32 ` Jiri Slaby
2024-02-23 11:51 ` [PATCH 4/4] kfifo: fix typos in kernel-doc Jiri Slaby (SUSE)
2024-02-23 12:08 ` Jiri Slaby [this message]
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=53095fb1-1093-4db0-8c8b-ef3d7d673628@kernel.org \
--to=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefani@seibold.net \
/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®