search for: rase

Hi I cant figure out how to raise a number to a power in ruby. ANy ideas?? Thanks Chris -- Posted via http://www.ruby-forum.com/.

Hello, Using Icecast version 2.0.2, I'm seeing segfaults when I connect a particular encoder to the stream. I already have three encoders connected, serving six streams without a problem, but adding the seventh stream crashes Icecast everytime after a period of ten to thirty seconds. All but one of the encoders are Darkice encoders and the encoder which crashes Icecast is also Darkice. So

Does raising the domain level need to be done on all DC's running in the Forest or just one? How about the forest level? The wiki makes me believe only one is needed. Will rasing the functional levels prevent any samba4 version from joining the domain? I would like to raise my current 2003 level to 2008 to take advantage of the following features. * Advanced Encryption Standard (AES 128

On Mon, 2004-10-25 at 23:14, Myke Place wrote: > Hello, > > Using Icecast version 2.0.2, I'm seeing segfaults when I connect a > particular encoder to the stream. I already have three encoders > connected, serving six streams without a problem, but adding the seventh > stream crashes Icecast everytime after a period of ten to thirty > seconds. All but one of the encoders

On Tuesday 26 October 2004 08:22, Karl Heyes wrote: > On Mon, 2004-10-25 at 23:14, Myke Place wrote: > > Hello, > > > > Using Icecast version 2.0.2, I'm seeing segfaults when I connect a > > particular encoder to the stream. I already have three encoders > > connected, serving six streams without a problem, but adding the seventh > > stream crashes

...f course, if an application (X or not) was started from a connected terminal. I actually tested this just doing popen("ssh") from a test program and just starting it from the window manager menu) I guess the best way to fix that is to detect that condition in "readpass.c:read_passphrase()", and fallback to 'use_askpass'. However, I haven't found a way to do so :) poll() works fine, writing to the terminal doesn't rase TTOU immediately (yeah, how did read() trigger a TTOU ???) As a relief, I guess I'll restrict the readpassphrase to only restart limited am...

On Monday 24 November 2014 16:22:53 Hu Tao wrote: > On Fri, Nov 21, 2014 at 05:17:13PM +0100, Pino Toscano wrote: > > On Friday 21 November 2014 13:18:00 Hu Tao wrote: > > > btrfs_subvolume_show shows the detailed information of a subvolume > > > or > > > snapshot. > > > > > > Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> > > >

On Tue, Sep 10, 2019 at 04:19:35PM +0800, Jason Wang wrote: > This sample driver creates mdev device that simulate virtio net device > over virtio mdev transport. The device is implemented through vringh > and workqueue. > > Signed-off-by: Jason Wang <jasowang at redhat.com> > --- > samples/Kconfig | 7 + > samples/vfio-mdev/Makefile | 1 + >

This patch implements a software vDPA networking device. The datapath is implemented through vringh and workqueue. The device has an on-chip IOMMU which translates IOVA to PA. For kernel virtio drivers, vDPA simulator driver provides dma_ops. For vhost driers, set_map() methods of vdpa_config_ops is implemented to accept mappings from vhost. Currently, vDPA device simulator will loopback TX

This patch implements a software vDPA networking device. The datapath is implemented through vringh and workqueue. The device has an on-chip IOMMU which translates IOVA to PA. For kernel virtio drivers, vDPA simulator driver provides dma_ops. For vhost driers, set_map() methods of vdpa_config_ops is implemented to accept mappings from vhost. Currently, vDPA device simulator will loopback TX

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: 076cb4adba3e2d7d3c25b72a1390b24ebfc58161 commit: 076cb4adba3e2d7d3c25b72a1390b24ebfc58161 [22/22] virtio/test: fix up after IOTLB changes config: m68k-allmodconfig (attached as .config) compiler: m68k-linux-gcc (GCC) 9.3.0 reproduce: wget

This sample driver creates mdev device that simulate virtio net device over virtio mdev transport. The device is implemented through vringh and workqueue. A device specific dma ops is to make sure HVA is used directly as the IOVA. This should be sufficient for kernel virtio driver to work. Only 'virtio' type is supported right now. I plan to add 'vhost' type on top which requires

This sample driver creates mdev device that simulate virtio net device over virtio mdev transport. The device is implemented through vringh and workqueue. Signed-off-by: Jason Wang <jasowang at redhat.com> --- samples/Kconfig | 7 + samples/vfio-mdev/Makefile | 1 + samples/vfio-mdev/mvnet.c | 766 +++++++++++++++++++++++++++++++++++++ 3 files changed, 774 insertions(+)

This sample driver creates mdev device that simulate virtio net device over virtio mdev transport. The device is implemented through vringh and workqueue. A device specific dma ops is to make sure HVA is used directly as the IOVA. This should be sufficient for kernel virtio driver to work. Only 'virtio' type is supported right now. I plan to add 'vhost' type on top which requires

This sample driver creates mdev device that simulate virtio net device over virtio mdev transport. The device is implemented through vringh and workqueue. A device specific dma ops is to make sure HVA is used directly as the IOVA. This should be sufficient for kernel virtio driver to work. Only 'virtio' type is supported right now. I plan to add 'vhost' type on top which requires

This sample driver creates mdev device that simulate virtio net device over virtio mdev transport. The device is implemented through vringh and workqueue. A device specific dma ops is to make sure HVA is used directly as the IOVA. This should be sufficient for kernel virtio driver to work. Only 'virtio' type is supported right now. I plan to add 'vhost' type on top which requires

This sample driver creates mdev device that simulate virtio net device over virtio mdev transport. The device is implemented through vringh and workqueue. A device specific dma ops is to make sure HVA is used directly as the IOVA. This should be sufficient for kernel virtio driver to work. Only 'virtio' type is supported right now. I plan to add 'vhost' type on top which requires

On Mon, Feb 10, 2020 at 11:56:08AM +0800, Jason Wang wrote: > This patch implements a software vDPA networking device. The datapath > is implemented through vringh and workqueue. The device has an on-chip > IOMMU which translates IOVA to PA. For kernel virtio drivers, vDPA > simulator driver provides dma_ops. For vhost driers, set_map() methods > of vdpa_config_ops is implemented to

On Wed, Nov 06, 2019 at 09:35:31PM +0800, Jason Wang wrote: > This sample driver creates mdev device that simulate virtio net device > over virtio mdev transport. The device is implemented through vringh > and workqueue. A device specific dma ops is to make sure HVA is used > directly as the IOVA. This should be sufficient for kernel virtio > driver to work. > > Only

On Wed, Nov 06, 2019 at 09:35:31PM +0800, Jason Wang wrote: > This sample driver creates mdev device that simulate virtio net device > over virtio mdev transport. The device is implemented through vringh > and workqueue. A device specific dma ops is to make sure HVA is used > directly as the IOVA. This should be sufficient for kernel virtio > driver to work. > > Only