Searched refs:backends (Results 1 - 25 of 33) sorted by relevance

12

/barrelfish-2018-10-04/lib/net/
H A Dnetworking_internal.h24 #include <devif/backends/loopback_devif.h>
25 #include <devif/backends/net/sfn5122f_devif.h>
26 #include <devif/backends/net/e10k_devif.h>
27 #include <devif/backends/net/e1000_devif.h>
28 #include <devif/backends/net/mlx4_devif.h>
/barrelfish-2018-10-04/include/devif/backends/net/
H A Dudp.h14 #include <devif/backends/net/ip.h>
/barrelfish-2018-10-04/lib/vfs/
H A Dvfs_blockdevfs.c74 struct backend_ops backends[3] = { variable in typeref:struct:backend_ops
130 err = backends[cur->type].open(cur->backend_handle);
167 blockdevfs_ahci_read, backends[entry->type].read);
168 errval_t ret = backends[entry->type].read(entry->backend_handle, h->pos,
183 errval_t ret = backends[entry->type].write(entry->backend_handle, h->pos,
255 errval_t ret = backends[entry->type].close(entry->backend_handle);
318 return backends[entry->type].flush(entry->backend_handle);
/barrelfish-2018-10-04/doc/015-disk-driver-arch/
H A Dblockdevfs.tex6 The backends of blockdevfs can expose an arbitrary number of filenames. The
7 filenames from different backends are combined to form the root directory of
18 registered by blockdevfs backends in the order they were added to blockdevfs.
20 is used as an index into the \lstinline+backends+ array holding function
32 blockdevfs backends must use the \lstinline+blockdev_append_entry+ function to
45 backends to register their exported files. A backend can choose the
49 For standard \acs{vfs} operations, backends need to provide these four functions:
70 Upon mounting, blockdevfs initializes its backends which in turn populate the
76 Currently the block device file system has two backends. One backend uses
78 interface. The backends ar
[all...]
H A Dfuture.tex51 backends for other controllers. Since this lab project only examined
55 Therefore, backends for more chipsets should be developed, most importantly one
/barrelfish-2018-10-04/usr/tests/devif/
H A Didc_endpoint.c17 #include <devif/backends/descq.h>
18 #include <devif/backends/debug.h>
H A Ddebug_test.c18 #include <devif/backends/net/sfn5122f_devif.h>
19 #include <devif/backends/net/e10k_devif.h>
20 #include <devif/backends/debug.h>
21 #include <devif/backends/descq.h>
22 #include <devif/backends/null.h>
H A Dclient.c19 #include <devif/backends/net/udp.h>
H A Dbench.c17 #include <devif/backends/loopback_devif.h>
18 #include <devif/backends/debug.h>
19 #include <devif/backends/null.h>
H A Dqueue_interface.c18 #include <devif/backends/net/sfn5122f_devif.h>
19 #include <devif/backends/net/e10k_devif.h>
20 #include <devif/backends/descq.h>
H A Decho.c19 #include <devif/backends/net/udp.h>
H A Dudp_queue.c18 #include <devif/backends/net/udp.h>
/barrelfish-2018-10-04/lib/net_interfaces/
H A Dinterface_raw.c22 #include <devif/backends/descq.h>
24 #include <devif/backends/net/sfn5122f_devif.h>
25 #include <devif/backends/net/e10k_devif.h>
/barrelfish-2018-10-04/usr/drivers/ahcid/
H A Dahcid.c12 #include <devif/backends/blk/ahci_devq.h>
H A Dtest.c7 #include <devif/backends/blk/ahci_devq.h>
/barrelfish-2018-10-04/lib/devif/backends/loopback/
H A Dloopback_queue.c13 #include <devif/backends/loopback_devif.h>
/barrelfish-2018-10-04/lib/devif/backends/null/
H A Ddevif_backend_null.c16 #include <devif/backends/null.h>
/barrelfish-2018-10-04/lib/blk/blk_ahci/
H A Ddevice_impl.c5 #include <devif/backends/blk/ahci_devq.h>
/barrelfish-2018-10-04/lib/devif/backends/net/ip/
H A Ddevif_backend_ip.c18 #include <devif/backends/net/ip.h>
/barrelfish-2018-10-04/lib/devif/backends/net/udp/
H A Ddevif_backend_udp.c17 #include <devif/backends/net/udp.h>
/barrelfish-2018-10-04/doc/011-idc/
H A DIDC.tex302 single output file the results of one or more \emph{backends}. The names of the
303 input and output files and the backends to use are determined by the
341 UMP, or RCK backends; when specified, it must be one of the architectures
346 backends. The \emph{generic} backend defines the common interface and support
347 code that is shared by all other backends, and is always required.
353 Most Flounder backends generate message stubs for specific interconnect
1095 \chapter{Additional Flounder backends}
/barrelfish-2018-10-04/lib/net_sockets/
H A Dnet_sockets.c19 #include <devif/backends/descq.h>
/barrelfish-2018-10-04/usr/drivers/e1000/
H A Ddevif_backend_e1000.c15 #include <devif/backends/net/e1000_devif.h>
/barrelfish-2018-10-04/usr/drivers/solarflare/
H A Ddevif_backend_solarflare.c20 #include <devif/backends/net/sfn5122f_devif.h>
/barrelfish-2018-10-04/lib/devif/backends/idc/
H A Ddesc_queue.c13 #include <devif/backends/descq.h>

Completed in 107 milliseconds

12