Tools
Sorted by:
Try your query at:
 |
 |
 |
 |
 |
 |
Results 1 - 10
of
12,194
Table 6.2 allows to compare the characteristics of the USB subsystem (Linux kernel 2.4.20) and the OVCam (version 1.63) web-cam driver in different environments.
in 2 Contents
2003
Table 1: The three classes of shadow drivers and the Linux drivers tested. We present results for the boldfaced drivers only, as the others behaved similarly.
2004
"... In PAGE 9: ... We built and tested three Linux shadow drivers for three device-driver classes: network interface controller, sound card, and IDE storage device. To ensure that our generic shadow drivers worked consistently across device driver implementations, we tested them on thirteen differ- ent Linux drivers, shown in Table1 . Although we present detailed results for only one driver in each class (e1000, audigy, and ide-disk), behavior across all drivers was sim- ilar.... ..."
Cited by 48
Table 2: TCP Throughput (Mbps) with Di erent USB Modes FSBR Disabled FSBR Enabled
2003
"... In PAGE 7: ...n Section 3.2. These experiments used a 16 KB send socket bu er size, a 24 KB receive socket bu er size, and a 16 KB message size. Table2 shows the measured results. The mean and standard deviation are derived from repeating each experiment 10 times.... In PAGE 7: ... The values in bold font show the results with the default Linux USB setting. The results in Table2 show that the bottleneck shifts from the USB bus to the wireless network when FSBR is enabled. We elaborate on these results in the following.... In PAGE 7: ...he wireless network when FSBR is enabled. We elaborate on these results in the following. A. Queueless Mode The columns labeled Qless in Table2 show the results when the network card driver sends one packet at a time to the USB. That is, only after the USB transmits the previous TCP packet successfully does the driver submit the next TCP packet.... In PAGE 8: ... After guring out the bu er size, we modi ed the network adapter driver so that it sends USB requests continuously until the bu er is full. Table2 shows the results for Queued mode. Two observations are evident: When FSBR is disabled, the bottleneck is still the USB bus.... ..."
Cited by 2
TABLE 2. Results of Formal Verification
1995
Cited by 4
Table I. The Three Classes of Shadow Drivers and the Linux Drivers Tested
2004
Cited by 48
Table 2. Summary of Experimental Results: Linux Drivers
"... In PAGE 10: ... We believe this can be fixed by implementing an extended occurs check [24]. Table2 lists our results. We found a total of 4 races.... ..."
Table 2: Summary of Experimental Results: Linux Drivers
"... In PAGE 21: ... We believe this can be fixed by implementing an extended occurs check [26]. Table2 lists our results. We found a total of 4 races.... ..."
Table 3: Accuracy of signatures in formal verification
"... In PAGE 4: ... Here, signatures are used to find variable corre- spondences in pairs of Boolean functions prior to formal verifica- tion. The results are shown in Table3 . Even for large functions with many inputs few variable order aliases are observed.... ..."
Table 1. Formal verification using BAN logic.
"... In PAGE 9: ... The deduction is quite lengthy and we omit it. We only show the idealized protocol and stepwise results in Table1 and omit the detailed discussion of the process. Step 1 is trivial.... In PAGE 9: ... Since that member has the control over the generation of the Bloom filter, P believes the Bloom filter (Postulate (3)). Based on these postulates, we can mechanically deduct and get the results as shown in Table1 . Moreover, the logic forces us to explicitly write down our assumptions to clarify our design goals.... ..."
Results 1 - 10
of
12,194
