search for: descritor

...Can't find format unrecognized(1280070990) in the format lookup table wine: Unhandled page fault on write access to 0x6d3361d6 at address 0x71bd6b14 (thread 0047), starting debugger... err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7ef90418 wine client error:16: write: Descritor de arquivo inv?lido what this line means? Code: wine client error:16: write: Descritor de arquivo inv?lido Thanks[/code]

A quick status report on how 1.0rc8 behaved in service for a few hours with several hundred simultaneous users, at a site very new to dovecot. Oh, and a question at the end. Summary: Reasonable for a first shot but one significant problem, requiring backing off. Background: We have a long-established UW-IMAP service for a user population of about 20,000 based on a few Linux (Redhat) machines

...uct irq_affinity pointer to the find_vqs methods, which if set is used to tell the PCI layer to create the MSI-X vectors for our I/O virtqueues with the proper affinity from the start. Compared to after the fact affinity hints this gives us an instantly working setup and allows to allocate the irq descritors node-local and avoid interconnect traffic. Last but not least this will allow blk-mq queues are created based on the interrupt affinity for storage drivers. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/block/virtio_blk.c | 3 ++- drivers/char/virtio_consol...

Hi Michael, hi Jason, This patches applies a few cleanups to the virtio PCI interrupt handling code, and then converts the virtio PCI code to use the automatic MSI-X vectors spreading, as well as using the information in virtio-blk and virtio-scsi to automatically align the blk-mq queues to the MSI-X vectors. Changes since V1: - dropped the patches already merged for 4.10-rc - new patch to

Hi Michael, hi Jason, This patches applies a few cleanups to the virtio PCI interrupt handling code, and then converts the virtio PCI code to use the automatic MSI-X vectors spreading, as well as using the information in virtio-blk and virtio-scsi to automatically align the blk-mq queues to the MSI-X vectors. Changes since V1: - dropped the patches already merged for 4.10-rc - new patch to

Hi Michael, this series contains a couple cleanups for the virtio_pci interrupt handling code, including a switch to the new pci_irq_alloc_vectors helper, and support for automatic affinity by the PCI layer if the consumers ask for it. It then converts over virtio_blk to use this functionality so that it's blk-mq queues are aligned to the MSI-X vector routing. I have a similar patch in the

Hi Michael, this series contains a couple cleanups for the virtio_pci interrupt handling code, including a switch to the new pci_irq_alloc_vectors helper, and support for automatic affinity by the PCI layer if the consumers ask for it. It then converts over virtio_blk to use this functionality so that it's blk-mq queues are aligned to the MSI-X vector routing. I have a similar patch in the

Hi Michael, hi Jason, This patches applies a few cleanups to the virtio PCI interrupt handling code, and then converts the virtio PCI code to use the automatic MSI-X vectors spreading, as well as using the information in virtio-blk and virtio-scsi to automatically align the blk-mq queues to the MSI-X vectors. Changes since V2: - remove a redundant callback check - calculate ->msix_vectors

Hi Michael, hi Jason, This patches applies a few cleanups to the virtio PCI interrupt handling code, and then converts the virtio PCI code to use the automatic MSI-X vectors spreading, as well as using the information in virtio-blk and virtio-scsi to automatically align the blk-mq queues to the MSI-X vectors. Changes since V2: - remove a redundant callback check - calculate ->msix_vectors

...iating the proper ACR and adds a lot of flexibility that will be required as more firmwares get released. At the moment, released firmwares cover driver versions 352 (for GM20B) and 361 (for GM200, GM204, GM206 and GP100). The r361 implementation re-uses most of r352, and only implements its own BL descritors since the structure changed between the two versions. Other patches are a mix of minor optimizations (1, 2, 3, 4, 9, 10, 12, 13), small fixes (5, 7, 11), and addition of abstractions to properly support various ACR versions (6, 14). Not all the abstractions are used at the moment (particularly th...

...iating the proper ACR and adds a lot of flexibility that will be required as more firmwares get released. At the moment, released firmwares cover driver versions 352 (for GM20B) and 361 (for GM200, GM204, GM206 and GP100). The r361 implementation re-uses most of r352, and only implements its own BL descritors since the structure changed between the two versions. Other patches are a mix of minor optimizations (1, 2, 3, 4, 9, 10, 12, 13, 15), small fixes (5, 7, 11), and addition of abstractions to properly support various ACR versions (6, 14). Not all the abstractions are used at the moment (particularl...