search for: specificaiton

...things they want to archive are specified like so: /path/path/path/A/04?? /path/path/path/B/04?? /path/path/path/A/05?? /path/path/path/B/05?? /path/path/path/A/06?? /path/path/path/B/06?? ...and there are things in A and B which do not match the specifications. The total amount of data in this specificaiton is around 30GB, and this is not distributed equally through the specification. What I'm hoping for is a program that I can feed in directory specifications like the above, and it will produce for me DVD images (.iso files) containing these trees in such a format that when the engineers want fi...

...things they want to archive are specified like so: /path/path/path/A/04?? /path/path/path/B/04?? /path/path/path/A/05?? /path/path/path/B/05?? /path/path/path/A/06?? /path/path/path/B/06?? ...and there are things in A and B which do not match the specifications. The total amount of data in this specificaiton is around 30GB, and this is not distributed equally through the specification. What I'm hoping for is a program that I can feed in directory specifications like the above, and it will produce for me DVD images (.iso files) containing these trees in such a format that when the engineers want fi...

...39;ve got a HT-enabled dual-preocessor Xeon machine, on which I''m running xen-3.0-testing. I''ve specified entries like the following in the configuration scripts for DomU''s to prevent them running on CPU 0: cpus = "1-4, ^0" My question is 1. Does this type of specificaiton mean Dom0 would *always* be running on CPU0? Please note that this question is different from "if Dom0 will *only* run on CPU 0?" What I want to know is can be described with an example: Say, any of the DomU''s (running on CPUs other than 0) wants to do some I/O for which he need...

Hi Rob & Mihai, I wrote vhost-nvme patches on top of Christoph's NVMe target. vhost-nvme still uses mmio. So the guest OS can run unmodified NVMe driver. But the tests I have done didn't show competitive performance compared to virtio-blk/virtio-scsi. The bottleneck is in mmio. Your nvme vendor extension patches reduces greatly the number of MMIO writes. So I'd like to push it

Hi Rob & Mihai, I wrote vhost-nvme patches on top of Christoph's NVMe target. vhost-nvme still uses mmio. So the guest OS can run unmodified NVMe driver. But the tests I have done didn't show competitive performance compared to virtio-blk/virtio-scsi. The bottleneck is in mmio. Your nvme vendor extension patches reduces greatly the number of MMIO writes. So I'd like to push it