similar to: Finding the right interface on FreeBSD

Hello, I noticed some random crashes after sending SIGHUP to the daemon (especially when some connections are continually failling). Playing around with gdb, it seems that after SIGHUP, all the "outgoing" information of the connections is being cleared, but later on it is being used in other places while still equal to NULL. The attached patch tries to fix this by avoiding these

On Tue, Apr 10, 2018 at 10:52:52AM +0800, Jason Wang wrote: > On 2018?04?02? 23:23, Tiwei Bie wrote: > > This patch introduces a mdev (mediated device) based hardware > > vhost backend. This backend is an abstraction of the various > > hardware vhost accelerators (potentially any device that uses > > virtio ring can be used as a vhost accelerator). Some generic > >

On Tue, Apr 10, 2018 at 10:52:52AM +0800, Jason Wang wrote: > On 2018?04?02? 23:23, Tiwei Bie wrote: > > This patch introduces a mdev (mediated device) based hardware > > vhost backend. This backend is an abstraction of the various > > hardware vhost accelerators (potentially any device that uses > > virtio ring can be used as a vhost accelerator). Some generic > >

On 2019/7/3 ??5:13, Tiwei Bie wrote: > Details about this can be found here: > > https://lwn.net/Articles/750770/ > > What's new in this version > ========================== > > A new VFIO device type is introduced - vfio-vhost. This addressed > some comments from here: https://patchwork.ozlabs.org/cover/984763/ > > Below is the updated device interface: >

More details about this patch can be found from the cover letter for now. Only compile test has been done for now. Signed-off-by: Tiwei Bie <tiwei.bie at intel.com> --- drivers/vhost/Kconfig | 9 + drivers/vhost/Makefile | 3 + drivers/vhost/mdev.c | 462 +++++++++++++++++++++++++++++++ drivers/vhost/vhost.c | 39 ++- drivers/vhost/vhost.h

? 2023/2/8 17:42, Eugenio P?rez ??: > This allows net to restart the device backend to configure SVQ on it. > > Ideally, these changes should not be net specific. However, the vdpa net > backend is the one with enough knowledge to configure everything because > of some reasons: > * Queues might need to be shadowed or not depending on its kind (control > vs data). > *

On 2018?04?02? 23:23, Tiwei Bie wrote: > This patch introduces a mdev (mediated device) based hardware > vhost backend. This backend is an abstraction of the various > hardware vhost accelerators (potentially any device that uses > virtio ring can be used as a vhost accelerator). Some generic > mdev parent ops are provided for accelerator drivers to support > generating mdev

On 2019/9/17 ??9:02, Tiwei Bie wrote: > More details about this patch can be found from the cover > letter for now. Only compile test has been done for now. > > Signed-off-by: Tiwei Bie <tiwei.bie at intel.com> > --- > drivers/vhost/Kconfig | 9 + > drivers/vhost/Makefile | 3 + > drivers/vhost/mdev.c | 462

hello all i'm currently using passdb to enable and disable various namespaces conditionally : for example the following work namespace/inbox/inbox=no namespace/legacy_pfso/disabled=no namespace/legacy_pfso/inbox=no namespace/local_storage/disabled=no namespace/comboINBOX_local_pfso/disabled=no namespace/comboINBOX_local_pfso/inbox=yes but i can't get things like the following to work

Good afternoon, I've downloaded the newly released Samba package 2.0.0, and when trying to run "compile" (located in directory source of the package), after a moment, script fail with the following errors: >ERROR: No locking available. Running Samba would be unsafe >configure: error: summary failure. Aborting config. The following lines are extracted from last lines of

I think this isn't plj output. Please take a look : document printed from Foxit Reader(PDF), all works fine: LINK: http://img526.imageshack.us/my.php?image=digitalizar10001rw2.jpg error_log output using Foxit Reader: D [18/May/2007:13:27:58 -0300] cupsdAcceptClient: 9 from localhost:631 (IPv4) D [18/May/2007:13:27:58 -0300] cupsdReadClient: 9 POST /printers/teste_ HTTP/1.1 D

This patch introduces a mdev (mediated device) based hardware vhost backend. This backend is an abstraction of the various hardware vhost accelerators (potentially any device that uses virtio ring can be used as a vhost accelerator). Some generic mdev parent ops are provided for accelerator drivers to support generating mdev instances. What's this =========== The idea is that we can setup a

This patch introduces a mdev (mediated device) based hardware vhost backend. This backend is an abstraction of the various hardware vhost accelerators (potentially any device that uses virtio ring can be used as a vhost accelerator). Some generic mdev parent ops are provided for accelerator drivers to support generating mdev instances. What's this =========== The idea is that we can setup a

Details about this can be found here: https://lwn.net/Articles/750770/ What's new in this version ========================== A new VFIO device type is introduced - vfio-vhost. This addressed some comments from here: https://patchwork.ozlabs.org/cover/984763/ Below is the updated device interface: Currently, there are two regions of this device: 1) CONFIG_REGION

Details about this can be found here: https://lwn.net/Articles/750770/ What's new in this version ========================== A new VFIO device type is introduced - vfio-vhost. This addressed some comments from here: https://patchwork.ozlabs.org/cover/984763/ Below is the updated device interface: Currently, there are two regions of this device: 1) CONFIG_REGION

This RFC is to demonstrate below ideas, a) Build vhost-mdev on top of the same abstraction defined in the virtio-mdev series [1]; b) Introduce /dev/vhost-mdev to do vhost ioctls and support setting mdev device as backend; Now the userspace API looks like this: - Userspace generates a compatible mdev device; - Userspace opens this mdev device with VFIO API (including doing IOMMU

This RFC is to demonstrate below ideas, a) Build vhost-mdev on top of the same abstraction defined in the virtio-mdev series [1]; b) Introduce /dev/vhost-mdev to do vhost ioctls and support setting mdev device as backend; Now the userspace API looks like this: - Userspace generates a compatible mdev device; - Userspace opens this mdev device with VFIO API (including doing IOMMU

Hy, I'am trying to compile a little project with Borland C++ 5 on my redhat 7.0 box with the rpm package from linux-easy for wine. The IDE is working correctly, compilation goes ok but when comes time to link all object files together Borland c++ stop to work. I tried to export project file and do a make, it is the same problem ilink32.exe seems to hang.... Thanks for help Jean-Francois

I try to install wine20000909-1mdk for Mandrake7.2. But when I try 'wine sol' (just for the test) it says: '/usr/X11R6/bin/wine-strip: error in loading shared library: libavifil32.so: cannot open shared object file: No such file or directory' what's wrong? libavifil32.so exists (/usr/X11R6/lib/). TBA and sorry for my poor english.

MailMarshal (an automated content monitoring gateway) has not delivered the following message: Message: B0000c89bd.00000001.mml From: samba@samba.org To: lianaj@balgrammar.vic.edu.au Subject: Question This is due to automatic rules that have determined that the intended recipient is not authorized to receive messages with certain potentially dangerous filetypes attached.