Searched refs:bulk (Results 1 - 9 of 9) sorted by relevance
| /barrelfish-2018-10-04/lib/rcce/ |
| H A D | internal.h | 51 uintptr_t id, bulk; member in struct:msg_buf
|
| H A D | rcce.c | 247 assert(mb->bulk);
253 assert(!mb->bulk);
261 assert(mb->bulk);
|
| H A D | ring_barriers.c | 97 m->bulk = false;
132 m->bulk = true;
208 // XXX: Assert we can always send a big buffer as bulk data for performance
248 // Send via bulk transfer
266 dprintf("waiting for bulk reply\n");
|
| /barrelfish-2018-10-04/usr/ramfsd/ |
| H A D | service.c | 47 struct bulk_transfer_slave bulk; member in struct:client_state
148 // Init the bulk transfer library
149 err = bulk_slave_init(bulk_pool, bulk_size, &st->bulk);
335 // determine local address of bulk buffer
337 void *bulkbuf = bulk_slave_buf_get_mem(&st->bulk, bulkid, &bulk_size);
339 // limit max len to size of bulk buffer
350 // copy data to bulk buffer
352 // prepare bulk buffer for reply
353 bulk_slave_prepare_send(&st->bulk, bulkid);
376 // determine local address of bulk buffe
[all...] |
| /barrelfish-2018-10-04/lib/vfs/ |
| H A D | vfs_ramfs.c | 23 /// configuration setting to use bulk data (TODO: make this a mount option?)
31 struct bulk_transfer bulk; member in struct:ramfs_client
312 struct bulk_buf *buf = bulk_alloc(&cl->bulk);
363 err = bulk_free(&cl->bulk, bufid);
384 struct bulk_buf *buf = bulk_alloc(&cl->bulk);
426 err = bulk_free(&cl->bulk, bulk_buf_get_id(buf));
846 // Init bulk data lib
849 &client->bulk);
854 // Send bulk frame cap to server
|
| /barrelfish-2018-10-04/doc/014-bulk-transfer/ |
| H A D | bulk-transfer.tex | 42 domain bulk transport for Barrelfish. This chapter gives a motivation
44 implementations of bulk-transport in Barrelfish and reasoning
47 already convinced of the need for better bulk-transport in
52 There are two bulk transport mechanisms that exist in the current(as of August
54 \texttt{$lib/barrelfish/bulk\_transfer.c$}
58 \subsection{$bulk\_transfer.c/h$}
59 This is the official bulk transfer method supported by Barrelfish. In brief, this
66 bulk transfer is responsible for managing these blocks. This responsibility
72 So, this bulk transfer facility works in master-slave setup. The master
85 co-operative and willing to follow the protocol set for using the bulk
[all...] |
| /barrelfish-2018-10-04/usr/eclipseclp/documents/embedding/ |
| H A D | embed.tex | 499 \item[Sharing:] The bulk of the data is left in its original representation,
|
| /barrelfish-2018-10-04/usr/eclipseclp/documents/applications/ |
| H A D | tutorial.tex | 109 The tutorial follows a top-down methodology for the design of an application. Chapter~\ref{highleveldesign} discusses general issues of modular design and self-documenting code for ECLiPSe programs. The next chapter on data structures compares different ways of representing data internally and externally, and presents a canonical multi-representation format which allows effective access to data in all parts of an application. Chapter~\ref{gettingittowork} shows how to convert a high level specification into an executable program early in the development stage. The bulk of the tutorial is contained in chapter~\ref{programmingconcepts}, where we present a number of different programming concepts which can be used as development templates to solve particular problems. This is followed by chapter~\ref{inputoutput} on input/output, a particularly important aspect of developing extensible programs. The last two chapters deal with debugging (chapter~\ref{ifitdoesntwork}) and testing (chapter~\ref{correctnessandperformance}).
|
| /barrelfish-2018-10-04/lib/tommath/ |
| H A D | tommath.tex | 4458 a division by $\beta^m$ can be simulated virtually for free. The loop on line 64 performs the bulk of the work (\textit{corresponds to step 4 of algorithm 7.11})
|
Completed in 103 milliseconds