Gregory Haskins wrote: >>> >>> >> Or, my preference, have a small sglist in the descriptor; >> > > > Define "small" ;) >
4. > There a certainly patterns that cannot/will-not take advantage of SG > (for instance, your typical network rx path), and therefore the sg > entries are wasted in some cases. Since they need to be (IMHO) u64, > they suck down at least 8 bytes a piece. Because of this I elected to > use the model of one pointer per descriptor, with an external descriptor > for SG. What are your thoughts on this? > Measurement will tell. I have a feeling that it won't really matter, so maybe an external sglist is best. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
