search for: port3

I developed some code that called subroutines from the Port3 Library (http://www-out.bell-labs.com/project/PORT/). I?m thinking about making it available as an R package. But I?m not sure if their NON-EXCLUSIVE SOURCE CODE LICENSE AGREEMENT ( http://www-out.bell-labs.com/topic/swdist/licenses/nesource.txt ) permits this. I tried contacting the contact per...

...low the driver node */ + subgraph cluster_driver { + fillcolor = grey; + style = filled; + driver -> {payload1, payload2} [dir=none]; + } + + /* Driver malloc references */ + edge [style=dashed]; + driver -> port1; + driver -> port2; + driver -> port3:e; + driver -> port4; + + payload1:s -> port1:e; + payload2:s -> port3:e; + edge [style=""]; + + subgraph cluster_topology { + label="Topology Manager"; + labelloc=bottom; + + /* Topology references */ + mstb1 -> {port1, por...

...low the driver node */ + subgraph cluster_driver { + fillcolor = grey; + style = filled; + driver -> {payload1, payload2} [dir=none]; + } + + /* Driver malloc references */ + edge [style=dashed]; + driver -> port1; + driver -> port2; + driver -> port3:e; + driver -> port4; + + payload1:s -> port1:e; + payload2:s -> port3:e; + edge [style=""]; + + subgraph cluster_topology { + label="Topology Manager"; + labelloc=bottom; + + /* Topology references */ + mstb1 -> {port1, por...

...-1.dot new file mode 100644 index 000000000000..fb83789e0a3e --- /dev/null +++ b/Documentation/gpu/dp-mst/topology-figure-1.dot @@ -0,0 +1,31 @@ +digraph T { + /* Topology references */ + node [shape=oval]; + mstb1 -> {port1, port2}; + port1 -> mstb2; + port2 -> mstb3 -> {port3, port4}; + port3 -> mstb4; + + /* Malloc references */ + edge [style=dashed]; + mstb4 -> port3; + {port4, port3} -> mstb3; + mstb3 -> port2; + mstb2 -> port1; + {port1, port2} -> mstb1; + + edge [dir=back]; + node [style=filled;shape=box;fillcolor=lig...

...0..fb83789e0a3e > --- /dev/null > +++ b/Documentation/gpu/dp-mst/topology-figure-1.dot > @@ -0,0 +1,31 @@ > +digraph T { > + /* Topology references */ > + node [shape=oval]; > + mstb1 -> {port1, port2}; > + port1 -> mstb2; > + port2 -> mstb3 -> {port3, port4}; > + port3 -> mstb4; > + > + /* Malloc references */ > + edge [style=dashed]; > + mstb4 -> port3; > + {port4, port3} -> mstb3; > + mstb3 -> port2; > + mstb2 -> port1; > + {port1, port2} -> mstb1; > + > + edge [dir...

.../topology-figure-1.dot > > > @@ -0,0 +1,31 @@ > > > +digraph T { > > > + /* Topology references */ > > > + node [shape=oval]; > > > + mstb1 -> {port1, port2}; > > > + port1 -> mstb2; > > > + port2 -> mstb3 -> {port3, port4}; > > > + port3 -> mstb4; > > > + > > > + /* Malloc references */ > > > + edge [style=dashed]; > > > + mstb4 -> port3; > > > + {port4, port3} -> mstb3; > > > + mstb3 -> port2; > > > + mst...

...> +++ b/Documentation/gpu/dp-mst/topology-figure-1.dot > > @@ -0,0 +1,31 @@ > > +digraph T { > > + /* Topology references */ > > + node [shape=oval]; > > + mstb1 -> {port1, port2}; > > + port1 -> mstb2; > > + port2 -> mstb3 -> {port3, port4}; > > + port3 -> mstb4; > > + > > + /* Malloc references */ > > + edge [style=dashed]; > > + mstb4 -> port3; > > + {port4, port3} -> mstb3; > > + mstb3 -> port2; > > + mstb2 -> port1; > > + {port1, p...

I am using a custom qemu to launch a vhost enabled VM. The qemu doesn't use the default "/dev/vhost-net" directory as character device. Due to this I am getting the error: qemu-system-x86_64: -netdev type=tap,id=net1,script=no,downscript=no,ifname=port3,vhost=on: vhost-net requested but could not be initialized ​Is there a way to tell libvirt to ​avoid using the default /dev/vhost-net file? I have tried using the pass-through arguments but libvirt still processes the command and throws the error. PS: I can successfully create a vhost VM using q...

...and that I use to launch my qemu VM: qemu-system-x86_64 -cpu host -boot order=c -hda /root/Disks/ubuntu1.qcow2 -m 1024M -smp 2 --enable-kvm -name 'client 1' -nographic -vnc :2 -net none -no-reboot -mem-path /dev/hugepages -mem-prealloc -netdev type=tap,id=net1,script=no,downscript=no,ifname=port3,vhost=on -device virtio-net-pci,netdev=net1,mac=00:00:00:00:00:01,csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off -netdev type=tap,id=net2,script=no,downscript=no,ifname=port4,vhost=on -device virtio-net-pci,netdev=net2,mac=00:00:00:00:00:02,csum=off,gso=off,guest_tso4=off,guest_tso6=o...

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

...t; I am using a custom qemu to launch a vhost enabled VM. The qemu doesn't > use the default "/dev/vhost-net" directory as character device. Due to this > I am getting the error: > > > > qemu-system-x86_64: -netdev > type=tap,id=net1,script=no,downscript=no,ifname=port3,vhost=on: vhost-net > requested but could not be initialized > > > > ​Is there a way to tell libvirt to ​avoid using the default > /dev/vhost-net file? > > > > I have tried using the pass-through arguments but libvirt still processes > the command and throws the err...

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

...tus: NEW Severity: normal Priority: P5 Component: NAT Assignee: netfilter-buglog at lists.netfilter.org Reporter: antonio.ojea.garcia at gmail.com Scenario: There is one established connection IP1:Port1 -> IP2:Port2 There is a DNAT rule like IP3:Port3 -> IP2:Port2 If a new connection is created from IP1 to IP3:Port3, and this connection has source port Port1, the connection can not be established, because the incoming packet is not de-natted The bug was originally reported in Kubernetes: https://github.com/kubernetes/kubernetes/issues/90258...

...eems to work, I can assign the PCI devices to my HVMs. The HVMs see the pci device and load their respective igb drivers, and ethtool -i eth0 works on each HVM, shows the drivers are loaded and the eth0 interfaces are up. Hvm0 - 82580.port0 Hvm1 - 82580.port1 Hvm2 - 82580.port2 Hvm3 - 82580.port3 However I don''t get any link at my switch for any of my ports. The problem seems to be that the link signal is provided by the igb driver (is that correct?), and since dom0 cannot bind the pci devices to the driver (since they need to be free for pci passthrough) I cannot establish a...

...ndstream gxp2160 secret = telefono [celular](office) description = samsung gt-s7562 secret = celular [fxs](office) description = fxs port1 secret = fxs [pstn](!) nat = no canreinvite = no dtmfmode = auto disallow = all allow = g722 allow = alaw allow = ulaw [pstn-in](pstn) description = pstn-in port3 type = user host = dynamic secret = pstn-in context = incoming-call [pstn-out](pstn) description = pstn-out port3 type = peer host = 192.168.1.4 extensions.conf --------------- [incoming-call] exten => _24872006,1,Answer() same => n,Dial(SIP/telefono) same => n,Hangup() [outgoing-call...

This is a WIP version of the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

...unch my qemu VM: > qemu-system-x86_64 -cpu host -boot order=c -hda /root/Disks/ubuntu1.qcow2 > -m 1024M -smp 2 --enable-kvm -name 'client 1' -nographic -vnc :2 -net none > -no-reboot -mem-path /dev/hugepages -mem-prealloc -netdev > type=tap,id=net1,script=no,downscript=no,ifname=port3,vhost=on -device > virtio-net-pci,netdev=net1,mac=00:00:00:00:00:01,csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off > -netdev type=tap,id=net2,script=no,downscript=no,ifname=port4,vhost=on > -device > virtio-net-pci,netdev=net2,mac=00:00:00:00:00:02,csum=off,gso=off,guest_t...

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a