doc/014-bulk-transfer/bulk-transfer.tex

289   \item \textbf{data-element:} The data-element is what generator
291   data-element.
294   interested consumers, reclaiming the memory when data-element
304   \item \textbf{Slot:} The contiguous piece of memory where data-element is
305   entirely or partially stored. A data-element can span over
332   particular data-element.  In network stack parlance, this
503   element in the consumer-queue.  This element should be of size
504   cache-line to avoid any cache-conflicts.  This element can be
511   element in the consumer-queue.  This element should be of size
512   cache-line to avoid any cache-conflicts.  This element can be
519   element in the consumer-queue.  This element can be modified by
565     \item \texttt{More:} As the data-element can span more than one
567     following which belongs to same data-element.  This flag is
575     this producer is dealing with one data-element at one time,
638   consumer whenever the consumer-queue is empty and new data-element
774   \item Data-element generated (from generator to producer): This
775   message informs the producer that there is new data-element in the
856   figure out which consumers this data-element should go.  The
882     As consumer is dealing with one data-element at a time,
940 Whenever consumer is done with accessing/consuming the data-element,
959 continuous memory to produce data-element then the size of
960 slot will be the size of biggest data-element.  If the
961 generator can DMA the data-element into multiple non-contiguous
963 the average data-element size.  In any case, the slot size
966 data element might get consumed by different consumer running
971 The dis-advantage of having slots of size of largest data-element
1065 classification of the data-element, it is explicitly copied into the
1110 specify where data-element should be generated (true zero copy