Displaying 20 results from an estimated 5000 matches similar to: "Lispvirt: porting Libvirt API for Common Lisp"
2019 Oct 07
0
[PATCH RFC net-next 1/2] drivers: net: virtio_net: Add tx_timeout stats field
Em seg, 7 de out de 2019 ?s 11:15, Julian Wiedmann <jwi at linux.ibm.com> escreveu:
>
> On 06.10.19 20:45, jcfaracco at gmail.com wrote:
> > From: Julio Faracco <jcfaracco at gmail.com>
> >
> > For debug purpose of TX timeout events, a tx_timeout entry was added to
> > monitor this special case: when dev_watchdog identifies a tx_timeout and
> > throw
2019 Oct 07
0
[PATCH RFC net-next 2/2] drivers: net: virtio_net: Add tx_timeout function
Em seg, 7 de out de 2019 ?s 04:51, Michael S. Tsirkin <mst at redhat.com> escreveu:
>
> On Sun, Oct 06, 2019 at 03:45:15PM -0300, jcfaracco at gmail.com wrote:
> > From: Julio Faracco <jcfaracco at gmail.com>
> >
> > To enable dev_watchdog, virtio_net should have a tx_timeout defined
> > (.ndo_tx_timeout). This is only a skeleton to throw a warn message.
2019 Oct 06
0
[PATCH RFC net-next 2/2] drivers: net: virtio_net: Add tx_timeout function
From: Julio Faracco <jcfaracco at gmail.com>
To enable dev_watchdog, virtio_net should have a tx_timeout defined
(.ndo_tx_timeout). This is only a skeleton to throw a warn message. It
notifies the event in some specific queue of device. This function
still counts tx_timeout statistic and consider this event as an error
(one error per queue), reporting it.
Signed-off-by: Julio Faracco
2019 Oct 07
0
[PATCH RFC net-next 0/2] drivers: net: virtio_net: Implement
On Sun, Oct 06, 2019 at 03:45:13PM -0300, jcfaracco at gmail.com wrote:
> From: Julio Faracco <jcfaracco at gmail.com>
>
> Driver virtio_net is not handling error events for TX provided by
> dev_watchdog. This event is reached when transmission queue is having
> problems to transmit packets. To enable it, driver should have
> .ndo_tx_timeout implemented. This serie has
2019 Oct 07
3
[PATCH RFC net-next 2/2] drivers: net: virtio_net: Add tx_timeout function
On Sun, Oct 06, 2019 at 03:45:15PM -0300, jcfaracco at gmail.com wrote:
> From: Julio Faracco <jcfaracco at gmail.com>
>
> To enable dev_watchdog, virtio_net should have a tx_timeout defined
> (.ndo_tx_timeout). This is only a skeleton to throw a warn message. It
> notifies the event in some specific queue of device. This function
> still counts tx_timeout statistic and
2019 Oct 07
3
[PATCH RFC net-next 2/2] drivers: net: virtio_net: Add tx_timeout function
On Sun, Oct 06, 2019 at 03:45:15PM -0300, jcfaracco at gmail.com wrote:
> From: Julio Faracco <jcfaracco at gmail.com>
>
> To enable dev_watchdog, virtio_net should have a tx_timeout defined
> (.ndo_tx_timeout). This is only a skeleton to throw a warn message. It
> notifies the event in some specific queue of device. This function
> still counts tx_timeout statistic and
2015 Jul 01
0
[RFC] virtio_net: Adding tx_timeout function.
On Wed, Jun 24, 2015 at 10:31:09PM -0300, Julio Faracco wrote:
> 2015-06-24 3:10 GMT-03:00 Michael S. Tsirkin <mst at redhat.com>:
> >
> > On Tue, Jun 23, 2015 at 10:44:29PM -0300, Julio Faracco wrote:
> > > virtio_net paravirtualized driver does not have a tx_timeout() function to
> > > guarantee that the driver will recover properly after receiving a
2016 May 12
2
Re: Dump network traffic from each VM.
Hi Daniel,
I changed the libvirt code to support "-net dump" because it is
more comfortable to me and to users here.
I don't know if it is interesting to the community, but... most of the
code is ready if someone needs.
Julio Cesar Faracco
2016-05-05 10:34 GMT-03:00 Daniel P. Berrange <berrange@redhat.com>:
> On Wed, May 04, 2016 at 12:37:14PM -0300, Julio Faracco wrote:
2015 Jun 25
0
[RFC] virtio_net: Adding tx_timeout function.
On 06/25/2015 09:31 AM, Julio Faracco wrote:
> 2015-06-24 3:10 GMT-03:00 Michael S. Tsirkin <mst at redhat.com>:
>> On Tue, Jun 23, 2015 at 10:44:29PM -0300, Julio Faracco wrote:
>>> virtio_net paravirtualized driver does not have a tx_timeout() function to
>>> guarantee that the driver will recover properly after receiving a timeout
>>> during a
2019 Oct 06
7
[PATCH RFC net-next 0/2] drivers: net: virtio_net: Implement
From: Julio Faracco <jcfaracco at gmail.com>
Driver virtio_net is not handling error events for TX provided by
dev_watchdog. This event is reached when transmission queue is having
problems to transmit packets. To enable it, driver should have
.ndo_tx_timeout implemented. This serie has two commits:
In the past, we implemented a function to recover driver state when this
kind of event
2019 Oct 06
7
[PATCH RFC net-next 0/2] drivers: net: virtio_net: Implement
From: Julio Faracco <jcfaracco at gmail.com>
Driver virtio_net is not handling error events for TX provided by
dev_watchdog. This event is reached when transmission queue is having
problems to transmit packets. To enable it, driver should have
.ndo_tx_timeout implemented. This serie has two commits:
In the past, we implemented a function to recover driver state when this
kind of event
2004 Feb 12
1
Porting let* from Common LISP to R
In porting some Common LISP code to R, I am trying to found out whether special
care must be taken for the let* function. In Common LISP, "the let* block
is like
let except it is guaranteed to evaluate the initialization of its local
variables in sequentially nested scopes, i.e. it provides an order to the
binding and visibility of preceding variables.".
I have included the recursive
2015 Jun 24
0
[RFC] virtio_net: Adding tx_timeout function.
On Tue, Jun 23, 2015 at 10:44:29PM -0300, Julio Faracco wrote:
> virtio_net paravirtualized driver does not have a tx_timeout() function to
> guarantee that the driver will recover properly after receiving a timeout
> during a transmission of a packet. This patch add this feature and throw a
> timeout exception after 5 HZ. Considering some tests, this is the best
> time to use here.
2015 Jul 02
1
[RFC] virtio_net: Adding tx_timeout function.
> On Wed, Jun 24, 2015 at 10:31:09PM -0300, Julio Faracco wrote:
> > 2015-06-24 3:10 GMT-03:00 Michael S. Tsirkin <mst at redhat.com>:
> > >
> > > On Tue, Jun 23, 2015 at 10:44:29PM -0300, Julio Faracco wrote:
> > > > virtio_net paravirtualized driver does not have a tx_timeout() function
> > > > to
> > > > guarantee that the
2015 Jul 02
1
[RFC] virtio_net: Adding tx_timeout function.
> On Wed, Jun 24, 2015 at 10:31:09PM -0300, Julio Faracco wrote:
> > 2015-06-24 3:10 GMT-03:00 Michael S. Tsirkin <mst at redhat.com>:
> > >
> > > On Tue, Jun 23, 2015 at 10:44:29PM -0300, Julio Faracco wrote:
> > > > virtio_net paravirtualized driver does not have a tx_timeout() function
> > > > to
> > > > guarantee that the
2009 Dec 02
1
Calling R (GNU R) functions from Common Lisp, how?
Hi Lisp users,
I'm a user of both Common Lisp and R (GNU R).
I found R has a rich collection of statistical and numerical
computation functions, while it is not as extensible as Lisp (Common
Lisp).
I considered Lisp-Stat but its only implementation is not in the
usuall Common Lisp, and the available functions in CRAN are far richer
than Lisp-Stat currently has.
I want to know if there is
2019 Nov 22
0
[PATCH net-next v2] drivers: net: virtio_net: Implement a dev_watchdog handler
On Thu, Nov 21, 2019 at 10:36:36PM -0300, Julio Faracco wrote:
> Driver virtio_net is not handling error events for TX provided by
> dev_watchdog. This event is reached when transmission queue is having
> problems to transmit packets. This could happen for any reason. To
> enable it, driver should have .ndo_tx_timeout implemented.
>
> This commit brings back virtnet_reset method
2016 May 04
2
Dump network traffic from each VM.
Hi guys,
Does anybody know how to dump the network trafic from each virtual
machine using libvirt?
Here, we usually use VPN softwares and other network tools inside
Virtual Machines (Windows and Linux). Sometimes, this applications
does not work properly, so we need to dump the network traffic of each
Virtual Machine to compare and debug.
How can I enable it using libvirt? I know that if you
2008 May 07
0
Ross Ihaka's reflections on Common Lisp and R
I came across a quite interesting post from Ross Ihaka, thought would be good
to share it and get the opinion of folks around here. I am not sure where to
post this for the R community but since it has to do with development I
thought or R-devel
Ross Ihaka
Newsgroups: comp.lang.lisp
From: Ross Ihaka <ih... at stat.auckland.ac.nz>
Date: Wed, 23 Jan 2008 10:35:26 +1300
Local: Tues, Jan 22
2020 Mar 17
0
new bquote feature splice does not address a common LISP @ use case?
Hi Jan,
In the lisp code you provide the operators are parsed as simple
symbols in a pairlist. In the R snippet, they are parsed as
left-associative binary operators of equal precedence. If you unquote
a call in the right-hand side, you're artificially bypassing the
left-associativity of these operators.
To achieve what you're looking for in a general way, you'll need a
more precise