search for: wqs

Hello, I'm author of Lsyncd - the live syncing deamon - http://code.google.com/p/lsyncd/ - a daemon that uses Linux` inotify to watch for filesystem changes - aggregates them for a few seconds and then periodically calls rsync to transfer the changes to target(s). Version 1 was simply aware of directories only, and it called rsync once with --delete -d for every directory in which anything

...out. Noted. I will say though that mlx5 uses prefetch and gets good performance because of it... > > > The interrupt handler is connected to the CQ, so an allocation of a single CQ > per core, with a single interrupt handler is possible although this core might be > using multiple WQs. > > Sending a single interrupt from multiple rings might save some > cycles. event index/interrupt disable are currently in > RAM so access is very cheap for the guest. > If you are going to share, just disable all interrupts > when you start processing. > > I was wonderi...

...out. Noted. I will say though that mlx5 uses prefetch and gets good performance because of it... > > > The interrupt handler is connected to the CQ, so an allocation of a single CQ > per core, with a single interrupt handler is possible although this core might be > using multiple WQs. > > Sending a single interrupt from multiple rings might save some > cycles. event index/interrupt disable are currently in > RAM so access is very cheap for the guest. > If you are going to share, just disable all interrupts > when you start processing. > > I was wonderi...

...nuous in memory so prefetching by the driver is efficient, although the device might complete work descriptors out of order. The interrupt handler is connected to the CQ, so an allocation of a single CQ per core, with a single interrupt handler is possible although this core might be using multiple WQs. One application for multiple WQs with a single CQ is Quality of Service(QoS). A user can open a WQ per QoS value(pcp value for example), and the device will schedule the work accordingly. > * Scatter/gather support > > We can use 1 bit to chain s/g entries in a request, same as virtio...

...e explicit? > > I agree, and it'd be great if we can find a solution such bugs can be detected > systematically (e.g. through lockdep), but maybe we can start to at least > document that we should never use the kernel global wq and where we need to be > careful in sharing driver wqs. Yeah I guess the above two are other reasons why maybe we need a bit more structure in scheduler apis instead of just allowing drivers to hand in shared wq pointers. Something like a struct drm_sched_domain, which contains the wq + a list of drm_sched for it. Would also make stuff like reliably s...

...that was the case. It would be easy for you to add this code to current virtio drivers and/or devices and try it out. > The interrupt handler is connected to the CQ, so an allocation of a single CQ per core, with a single interrupt handler is possible although this core might be using multiple WQs. Sending a single interrupt from multiple rings might save some cycles. event index/interrupt disable are currently in RAM so access is very cheap for the guest. If you are going to share, just disable all interrupts when you start processing. I was wondering how do people want to do this in hard...

This is an update from v1 version. Changes: - update event suppression mechanism - separate options for indirect and direct s/g - lots of new features --- Performance analysis of this is in my kvm forum 2016 presentation. The idea is to have a r/w descriptor in a ring structure, replacing the used and available ring, index and descriptor buffer. * Descriptor ring: Guest adds descriptors with

This is an update from v1 version. Changes: - update event suppression mechanism - separate options for indirect and direct s/g - lots of new features --- Performance analysis of this is in my kvm forum 2016 presentation. The idea is to have a r/w descriptor in a ring structure, replacing the used and available ring, index and descriptor buffer. * Descriptor ring: Guest adds descriptors with

From: Dave Airlie <airlied at gmail.com> This patch adds a kms driver for the virtio gpu. The xorg modesetting driver can handle the device just fine, the framebuffer for fbcon is there too. Qemu patches for the host side are under review currently. The pci version of the device comes in two variants: with and without vga compatibility. The former has a extra memory bar for the vga

From: Dave Airlie <airlied at gmail.com> This patch adds a kms driver for the virtio gpu. The xorg modesetting driver can handle the device just fine, the framebuffer for fbcon is there too. Qemu patches for the host side are under review currently. The pci version of the device comes in two variants: with and without vga compatibility. The former has a extra memory bar for the vga