search for: cfv

...h> + +MODULE_LICENSE("GPL v2"); +MODULE_AUTHOR("Vicram Arv <vikram.arv at stericsson.com>"); +MODULE_AUTHOR("Sjur Brendeland <sjur.brandeland at stericsson.com>"); +MODULE_DESCRIPTION("Virtio CAIF Driver"); + +/* NAPI schedule quota */ +#define CFV_DEFAULT_QUOTA 32 + +/* Defaults used if virtio config space is unavailable */ +#define CFV_DEF_MTU_SIZE 4096 +#define CFV_DEF_HEADROOM 32 +#define CFV_DEF_TAILROOM 32 + +/* Required IP header alignment */ +#define IP_HDR_ALIGN 4 + +/* struct cfv_napi_contxt - NAPI context info + * @riov: IOV holdin...

...h> + +MODULE_LICENSE("GPL v2"); +MODULE_AUTHOR("Vicram Arv <vikram.arv at stericsson.com>"); +MODULE_AUTHOR("Sjur Brendeland <sjur.brandeland at stericsson.com>"); +MODULE_DESCRIPTION("Virtio CAIF Driver"); + +/* NAPI schedule quota */ +#define CFV_DEFAULT_QUOTA 32 + +/* Defaults used if virtio config space is unavailable */ +#define CFV_DEF_MTU_SIZE 4096 +#define CFV_DEF_HEADROOM 32 +#define CFV_DEF_TAILROOM 32 + +/* Required IP header alignment */ +#define IP_HDR_ALIGN 4 + +/* struct cfv_napi_contxt - NAPI context info + * @riov: IOV holdin...

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This patch-set introduces the CAIF Virtio Link layer driver. This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Regards, Sjur cc: Rusty Russell <rusty at rustcorp.com.au> cc: Ohad Ben-Cohen <ohad at wizery.com> cc: David S. Miller

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This patch-set introduces the CAIF Virtio Link layer driver. This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Regards, Sjur cc: Rusty Russell <rusty at rustcorp.com.au> cc: Ohad Ben-Cohen <ohad at wizery.com> cc: David S. Miller

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Changes since V1: - Use the new iov helper functions, and simplify iov handling. However this triggers compile warnings, as it takes struct iov while kernel api uses struct kiov - Introduced

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Changes since V1: - Use the new iov helper functions, and simplify iov handling. However this triggers compile warnings, as it takes struct iov while kernel api uses struct kiov - Introduced

This patch-set introduces the CAIF Virtio Link layer. The purpose is to communicate with a remote processor (a modem) over shared memory. Virtio is used as the transport mechanism, and the Remoteproc framework provides configuration and management of the Virtio rings and devices. The modem and Linux host may be on the same SoC, or connected over a shared memory interface such as LLI. Zero-Copy

This patch-set introduces the CAIF Virtio Link layer. The purpose is to communicate with a remote processor (a modem) over shared memory. Virtio is used as the transport mechanism, and the Remoteproc framework provides configuration and management of the Virtio rings and devices. The modem and Linux host may be on the same SoC, or connected over a shared memory interface such as LLI. Zero-Copy

...(1 + ItemType.c + Block | Subject) + (1 | Word) Data: lexdec AIC BIC logLik deviance 4788 4957 -2370 4740 Random effects: Groups Name Variance Std.Dev. Corr Word (Intercept) 1.66447 1.29014 Subject (Intercept) 0.50865 0.71320 ItemType.cFV-L 0.89270 0.94483 0.261 ItemType.cFV-R 1.26385 1.12421 0.210 0.978 ItemType.cFV-B 1.33556 1.15566 0.143 0.916 0.979 Blockpost 0.93878 0.96891 -0.349 -0.093 0.037 0.163 Number of obs: 8500, groups: Word, 298; Subject, 17 Fixed...

...if_virtio.c b/drivers/net/caif/caif_virtio.c index f6caa1e..fb80765 100644 --- a/drivers/net/caif/caif_virtio.c +++ b/drivers/net/caif/caif_virtio.c @@ -318,7 +318,7 @@ exit: /* Really out of patckets? (stolen from virtio_net)*/ napi_complete(napi); - if (unlikely(vringh_notify_enable_kern(cfv->vr_rx)) && + if (unlikely(!vringh_notify_enable_kern(cfv->vr_rx)) && napi_schedule_prep(napi)) { vringh_notify_disable_kern(cfv->vr_rx); __napi_schedule(napi); -- 1.7.9.5

...if_virtio.c b/drivers/net/caif/caif_virtio.c index f6caa1e..fb80765 100644 --- a/drivers/net/caif/caif_virtio.c +++ b/drivers/net/caif/caif_virtio.c @@ -318,7 +318,7 @@ exit: /* Really out of patckets? (stolen from virtio_net)*/ napi_complete(napi); - if (unlikely(vringh_notify_enable_kern(cfv->vr_rx)) && + if (unlikely(!vringh_notify_enable_kern(cfv->vr_rx)) && napi_schedule_prep(napi)) { vringh_notify_disable_kern(cfv->vr_rx); __napi_schedule(napi); -- 1.7.9.5

...nction to call when buffers are available */ + void (*notify)(struct vringh *); diff --git a/drivers/net/caif/caif_virtio.c b/drivers/net/caif/caif_virtio.c index d4f339c..e657277 100644 --- a/drivers/net/caif/caif_virtio.c +++ b/drivers/net/caif/caif_virtio.c @@ -433,0 +434,2 @@ static int cfv_probe(struct virtio_device *vdev) + struct vringh *vrhs; + vrh_callback_t *vrh_cbs = cfv_recv; @@ -446,2 +448,2 @@ static int cfv_probe(struct virtio_device *vdev) - cfv->vr_rx = rproc_virtio_new_vringh(vdev, RX_RING_INDEX, cfv_recv); - if (!cfv->vr_rx) + err = v...

...nction to call when buffers are available */ + void (*notify)(struct vringh *); diff --git a/drivers/net/caif/caif_virtio.c b/drivers/net/caif/caif_virtio.c index d4f339c..e657277 100644 --- a/drivers/net/caif/caif_virtio.c +++ b/drivers/net/caif/caif_virtio.c @@ -433,0 +434,2 @@ static int cfv_probe(struct virtio_device *vdev) + struct vringh *vrhs; + vrh_callback_t *vrh_cbs = cfv_recv; @@ -446,2 +448,2 @@ static int cfv_probe(struct virtio_device *vdev) - cfv->vr_rx = rproc_virtio_new_vringh(vdev, RX_RING_INDEX, cfv_recv); - if (!cfv->vr_rx) + err = v...

...o use predict with a glmmPQL model, where you want to predict the response for one factor in the model? Originally I used predict on a GLM (gamma, log link) in the following way: p.1<-predict(model1,data.frame(year=as.factor(xv),nafdiv=as.factor(rep(" 3N",length(xv))), duration=1000, cfv=as.factor(rep(106166,length(xv))), hooks=rep(1,length(xv))),type="response",se.fit=T) where model1 standardises catch rate and includes nafo area, year, duration of fishing sets, and vessel (cfv) as explanatory variables with an offset of hooks. To predict the years we had data for, we...

I want to use rsync to diff two folders (with checksum) by using dry-run and itemize changes like this: rsync -rni --checksum /dir1/ /dir2/> ~/Desktop/diff.log However, I read that in --dry-run rsync wont do checksums. Is this true? If it is, is there a way to force checksums i dry-run mode?

Aiming these for coming merge window. Nothing should change, but get ready for a non-guest-endian config transports, and > 32 features bits. Final one is just an overdue consolidation. Cheers, Rusty. Rusty Russell (7): virtio_config: introduce size-based accessors. virtio: use size-based config accessors. virtio_config: helpers for non-converting accessors. virtio_config: make

Aiming these for coming merge window. Nothing should change, but get ready for a non-guest-endian config transports, and > 32 features bits. Final one is just an overdue consolidation. Cheers, Rusty. Rusty Russell (7): virtio_config: introduce size-based accessors. virtio: use size-based config accessors. virtio_config: helpers for non-converting accessors. virtio_config: make

...21:57:02 -0500 > From: kmk at sanitarium.net > To: rsync at lists.samba.org > Subject: Re: How to force checksum in dry-run > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > It will work but why not just use diff -r ? Or a dedicated file > validation utility like cfv? > > Rsync isn't even smart enough to not bother checksumming things that > don't even have a comparison file. > > On 12/20/2014 09:42 PM, eightfold ? wrote: > > I want to use rsync to diff two folders (with checksum) by using > > dry-run and itemize changes lik...

...; if (ret) { DRM_ERROR("failed to find virt queues\n"); goto err_vqs; diff --git a/drivers/net/caif/caif_virtio.c b/drivers/net/caif/caif_virtio.c index bc0eb47..6122768 100644 --- a/drivers/net/caif/caif_virtio.c +++ b/drivers/net/caif/caif_virtio.c @@ -679,8 +679,7 @@ static int cfv_probe(struct virtio_device *vdev) goto err; /* Get the TX virtio ring. This is a "guest side vring". */ - err = vdev->config->find_vqs(vdev, 1, &cfv->vq_tx, &vq_cbs, &names, - NULL); + err = virtio_find_vqs(vdev, 1, &cfv->vq_tx, &vq_cbs, &names...

...; if (ret) { DRM_ERROR("failed to find virt queues\n"); goto err_vqs; diff --git a/drivers/net/caif/caif_virtio.c b/drivers/net/caif/caif_virtio.c index bc0eb47..6122768 100644 --- a/drivers/net/caif/caif_virtio.c +++ b/drivers/net/caif/caif_virtio.c @@ -679,8 +679,7 @@ static int cfv_probe(struct virtio_device *vdev) goto err; /* Get the TX virtio ring. This is a "guest side vring". */ - err = vdev->config->find_vqs(vdev, 1, &cfv->vq_tx, &vq_cbs, &names, - NULL); + err = virtio_find_vqs(vdev, 1, &cfv->vq_tx, &vq_cbs, &names...