Go to file
Tom Burdick e4b10328b4 rtio: Use mpsc for submission and completion queue
Rather than the rings, which weren't shared between userspace and kernel
space in Zephyr like they are in Linux with io_uring, use atomic mpsc
queues for submission and completion queues.

Most importantly this removes a potential head of line blocker in the
submission queue as the sqe would be held until a task is completed.

As additional bonuses this avoids some additional locks and restrictions
about what can be submitted and where. It also removes the need for
two executors as all chains/transactions are done concurrently.

Lastly this opens up the possibility for a common pool of sqe's to
allocate from potentially saving lots of memory.

Signed-off-by: Tom Burdick <thomas.burdick@intel.com>
2023-05-10 00:39:43 +09:00
.github ci: bsim workflow: Update bsim to version pointed by manifest 2023-05-04 19:51:20 +09:00
arch arch: x86: pin boot arg before paging is up 2023-05-09 13:04:08 +02:00
boards soc: esp32s3: add usb serial dts interface 2023-05-09 14:31:23 +02:00
cmake libc: Move strnlen into common 2023-05-08 09:59:27 +02:00
doc doc: services: device_mgmt: smp_groups: img_mgmt: Add sha has note 2023-05-09 14:29:05 +02:00
drivers rtio: Use mpsc for submission and completion queue 2023-05-10 00:39:43 +09:00
dts dts: intel: Add dtsi entry for SiP SMC call. 2023-05-09 08:46:50 -04:00
include/zephyr rtio: Use mpsc for submission and completion queue 2023-05-10 00:39:43 +09:00
kernel kernel: idle: fix build error on arm-clang 2023-05-02 15:01:24 -05:00
lib lib: getopt: Fix compiler warning. 2023-05-09 11:03:44 -04:00
misc
modules drivers/sensor: add support to LSM6DSO16IS IMU sensor 2023-05-09 16:23:15 +09:00
samples rtio: Use mpsc for submission and completion queue 2023-05-10 00:39:43 +09:00
scripts twister: Bring back scope selection rule using platform_allow 2023-05-08 11:18:44 +02:00
share sysbuild: Add SB_OVERLAY_CONFIG 2023-05-05 09:42:10 +02:00
snippets snippets: add cdc-acm-console 2023-03-26 16:12:41 +02:00
soc riscv: Microchip Mi-V should use built-in atomic operations 2023-05-09 13:04:27 +02:00
submanifests
subsys rtio: Use mpsc for submission and completion queue 2023-05-10 00:39:43 +09:00
tests rtio: Use mpsc for submission and completion queue 2023-05-10 00:39:43 +09:00
.checkpatch.conf checkpatch: Remove ext/ from excludes 2022-11-30 12:06:55 -05:00
.clang-format clang-format: UseTab use ForContinuationAndIndentation 2023-05-05 11:06:54 -04:00
.codecov.yml yamllint: fix all yamllint comments errors 2023-01-04 01:16:45 +09:00
.editorconfig
.gitattributes
.gitignore tests bsim/net: Separate bsim networking and bluetooth tests. 2023-04-12 22:42:03 +09:00
.gitlint
.mailmap mailmap: add two fixes for bad commits 2023-03-17 08:08:16 -04:00
.yamllint scripts: compliance: add support for YAMLLint 2023-01-04 17:29:23 +01:00
CMakeLists.txt compiler: add CONFIG_COMPILER_TRACK_MACRO_EXPANSION 2023-05-05 12:08:48 +02:00
CODE_OF_CONDUCT.md
CODEOWNERS CODEOWNER: Add code owner for sip_svc subsystem 2023-05-09 08:46:50 -04:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr compiler: add CONFIG_COMPILER_TRACK_MACRO_EXPANSION 2023-05-05 12:08:48 +02:00
LICENSE
MAINTAINERS.yml maintainers: make gmarull the maintainer of the device driver model area 2023-05-09 09:24:21 +02:00
README.rst readme: Add support for light/dark modes in the logo 2022-11-18 08:58:59 +01:00
VERSION VERSION: Bump to 3.3.99 2023-02-19 20:34:26 +09:00
version.h.in
west.yml manifest: update Xtensa hal 2023-05-08 13:06:12 -05:00
zephyr-env.cmd
zephyr-env.sh

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <picture>
         <source media="(prefers-color-scheme: dark)" srcset="doc/_static/images/logo-readme-dark.svg">
         <source media="(prefers-color-scheme: light)" srcset="doc/_static/images/logo-readme-light.svg">
         <img src="doc/_static/images/logo-readme-light.svg">
       </picture>
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <a
   href="https://github.com/zephyrproject-rtos/zephyr/actions/workflows/twister.yaml?query=branch%3Amain">
   <img
   src="https://github.com/zephyrproject-rtos/zephyr/actions/workflows/twister.yaml/badge.svg?event=push"></a>


The Zephyr Project is a scalable real-time operating system (RTOS) supporting
multiple hardware architectures, optimized for resource constrained devices,
and built with security in mind.

The Zephyr OS is based on a small-footprint kernel designed for use on
resource-constrained systems: from simple embedded environmental sensors and
LED wearables to sophisticated smart watches and IoT wireless gateways.

The Zephyr kernel supports multiple architectures, including ARM (Cortex-A,
Cortex-R, Cortex-M), Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V,
SPARC, MIPS, and a large number of `supported boards`_.

.. below included in doc/introduction/introduction.rst


Getting Started
***************

Welcome to Zephyr! See the `Introduction to Zephyr`_ for a high-level overview,
and the documentation's `Getting Started Guide`_ to start developing.

.. start_include_here

Community Support
*****************

Community support is provided via mailing lists and Discord; see the Resources
below for details.

.. _project-resources:

Resources
*********

Here's a quick summary of resources to help you find your way around:

* **Help**: `Asking for Help Tips`_
* **Documentation**: http://docs.zephyrproject.org (`Getting Started Guide`_)
* **Source Code**: https://github.com/zephyrproject-rtos/zephyr is the main
  repository; https://elixir.bootlin.com/zephyr/latest/source contains a
  searchable index
* **Releases**: https://github.com/zephyrproject-rtos/zephyr/releases
* **Samples and example code**: see `Sample and Demo Code Examples`_
* **Mailing Lists**: users@lists.zephyrproject.org and
  devel@lists.zephyrproject.org are the main user and developer mailing lists,
  respectively. You can join the developer's list and search its archives at
  `Zephyr Development mailing list`_. The other `Zephyr mailing list
  subgroups`_ have their own archives and sign-up pages.
* **Nightly CI Build Status**: https://lists.zephyrproject.org/g/builds
  The builds@lists.zephyrproject.org mailing list archives the CI nightly build results.
* **Chat**: Real-time chat happens in Zephyr's Discord Server. Use
  this `Discord Invite`_ to register.
* **Contributing**: see the `Contribution Guide`_
* **Wiki**: `Zephyr GitHub wiki`_
* **Issues**: https://github.com/zephyrproject-rtos/zephyr/issues
* **Security Issues**: Email vulnerabilities@zephyrproject.org to report
  security issues; also see our `Security`_ documentation. Security issues are
  tracked separately at https://zephyrprojectsec.atlassian.net.
* **Zephyr Project Website**: https://zephyrproject.org

.. _Discord Invite: https://chat.zephyrproject.org
.. _supported boards: http://docs.zephyrproject.org/latest/boards/index.html
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Introduction to Zephyr: http://docs.zephyrproject.org/latest/introduction/index.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/develop/getting_started/index.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/index.html
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Development mailing list: https://lists.zephyrproject.org/g/devel
.. _Zephyr mailing list subgroups: https://lists.zephyrproject.org/g/main/subgroups
.. _Sample and Demo Code Examples: http://docs.zephyrproject.org/latest/samples/index.html
.. _Security: http://docs.zephyrproject.org/latest/security/index.html
.. _Asking for Help Tips: https://docs.zephyrproject.org/latest/develop/getting_started/index.html#asking-for-help