Searched full:liburing (Results 1 – 25 of 279) sorted by relevance
12345678910>>...12
| /external/liburing/src/ |
| D | Makefile | 19 soname=liburing.so.$(VERSION_MAJOR)
20 libname=liburing.so.$(VERSION)
21 all_targets += liburing.a
62 liburing.a: $(liburing_objs)
63 @rm -f liburing.a
64 $(QUIET_AR)$(AR) r liburing.a $^
65 $(QUIET_RANLIB)$(RANLIB) liburing.a
67 $(libname): $(liburing_sobjs) liburing.map
68 …$(QUIET_CC)$(CC) $(SO_CFLAGS) -shared -Wl,--version-script=liburing.map -Wl,-soname=$(soname) -o $…
71 install -D -m 644 include/liburing/io_uring.h $(includedir)/liburing/io_uring.h
[all …]
|
| D | syscall.c | 8 * liburing's tests still need these functions.
11 #error "This file should only be compiled for libc build, or for liburing tests"
20 #include "liburing/compat.h"
21 #include "liburing/io_uring.h"
|
| /external/liburing/debian/ |
| D | control | 1 Source: liburing
7 Homepage: https://git.kernel.dk/cgit/liburing/tree/README
8 Vcs-Git: https://git.kernel.dk/liburing
9 Vcs-Browser: https://git.kernel.dk/cgit/liburing/
19 system performance a lot. liburing is the userpace
32 system performance a lot. liburing is the userpace
37 Package: liburing-dev
45 system performance a lot. liburing is the userpace
|
| D | changelog | 1 liburing (0.7-1) stable; urgency=low
8 liburing (0.4-2) stable; urgency=low
10 * Fix /usr/lib/*/liburing.so symlink to /lib/*/liburing.so.1.0.4
14 liburing (0.4-1) stable; urgency=low
16 * Package liburing-0.4 using a packaging layout similar to libaio1
20 liburing (0.2-1ubuntu1) stable; urgency=low
|
| /external/liburing/ |
| D | liburing.spec | 1 Name: liburing
8 URL: https://git.kernel.dk/cgit/liburing/
38 %attr(0755,root,root) %{_libdir}/liburing.so.*
42 %{_includedir}/liburing/
43 %{_includedir}/liburing.h
44 %{_libdir}/liburing.so
45 %exclude %{_libdir}/liburing.a
|
| D | README | 1 liburing
4 This is the io_uring library, liburing. liburing provides helpers to setup and
22 liburing itself is not tied to any specific kernel release, and hence it's
23 possible to use the newest liburing release even on older kernels (and vice
45 The bulk of liburing is actually regression/unit tests for both liburing and
|
| D | .gitignore | 10 /src/liburing.a
11 /src/liburing.so*
12 /src/include/liburing/compat.h
27 liburing.pc
|
| D | METADATA | 1 name: "liburing"
8 value: "https://github.com/axboe/liburing"
12 value: "https://github.com/axboe/liburing"
|
| /external/liburing/test/ |
| D | Makefile | 198 # liburing nolibc.
201 # build liburing without libc, we don't have those functions
202 # in liburing.a. So build it manually here.
214 %.t: %.c $(helpers) helpers.h ../src/liburing.a
217 %.t: %.cc $(helpers) helpers.h ../src/liburing.a
222 $(INSTALL) -D -d -m 755 $(datadir)/liburing-test/
223 $(INSTALL) -D -m 755 $(test_targets) $(datadir)/liburing-test/
224 $(INSTALL) -D -m 755 runtests.sh $(datadir)/liburing-test/
225 $(INSTALL) -D -m 755 runtests-loop.sh $(datadir)/liburing-test/
|
| /external/liburing/man/ |
| D | io_uring_register_ring_fd.3 | 5 .TH io_uring_register_ring_fd 3 "March 11, 2022" "liburing-2.2" "liburing Manual"
10 .B #include <liburing.h>
31 If an application using liburing is threaded, then an application should call
|
| D | io_uring_free_probe.3 | 5 .TH io_uring_free_probe "January 25, 2022" "liburing-2.1" "liburing Manual"
10 .B #include <liburing.h>
|
| D | io_uring_unregister_files.3 | 5 .TH io_uring_unregister_files 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
10 .B #include <liburing.h>
|
| D | io_uring_buf_ring_mask.3 | 5 .TH io_uring_buf_ring_mask 3 "June 13, 2022" "liburing-2.2" "liburing Manual"
10 .B #include <liburing.h>
|
| D | io_uring_unregister_buffers.3 | 5 .TH io_uring_unregister_buffers 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
10 .B #include <liburing.h>
|
| D | io_uring_unregister_buf_ring.3 | 5 .TH io_uring_unregister_buf_ring 3 "May 18, 2022" "liburing-2.2" "liburing Manual"
10 .B #include <liburing.h>
|
| D | io_uring_buf_ring_init.3 | 5 .TH io_uring_buf_ring_init 3 "June 13, 2022" "liburing-2.2" "liburing Manual"
10 .B #include <liburing.h>
|
| D | io_uring_sq_space_left.3 | 5 .TH io_uring_sq_space-left "January 25, 2022" "liburing-2.1" "liburing Manual"
10 .B #include <liburing.h>
|
| D | io_uring_cq_ready.3 | 5 .TH io_uring_cq_ready "January 25, 2022" "liburing-2.1" "liburing Manual"
10 .B #include <liburing.h>
|
| D | io_uring_buf_ring_advance.3 | 5 .TH io_uring_buf_ring_advance 3 "May 18, 2022" "liburing-2.2" "liburing Manual"
10 .B #include <liburing.h>
|
| D | io_uring_queue_exit.3 | 6 .TH io_uring_queue_exit 3 "July 10, 2020" "liburing-0.7" "liburing Manual"
11 .B #include <liburing.h>
|
| D | io_uring_opcode_supported.3 | 5 .TH io_uring_opcode_supported "January 25, 2022" "liburing-2.1" "liburing Manual"
10 .B #include <liburing.h>
|
| D | io_uring_prep_openat.3 | 5 .TH io_uring_prep_openat 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
13 .B #include <liburing.h>
67 field, which is not a problem for liburing helpers, but users of the raw
|
| D | io_uring_prep_openat2_direct.3 | 5 .TH io_uring_prep_openat2 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
14 .B #include <liburing.h>
68 field, which is not a problem for liburing helpers, but users of the raw
|
| D | io_uring_prep_openat2.3 | 5 .TH io_uring_prep_openat2 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
14 .B #include <liburing.h>
68 field, which is not a problem for liburing helpers, but users of the raw
|
| D | io_uring_prep_openat_direct.3 | 5 .TH io_uring_prep_openat 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
13 .B #include <liburing.h>
67 field, which is not a problem for liburing helpers, but users of the raw
|
12345678910>>...12