search for: ida

Someone else also reported seeing these symptoms with recently-updated sources: >>> Kernel build for FREEBEAST started on Mon Sep 1 05:25:41 PDT 2003 ... ===> ida @ -> /usr/src/sys machine -> /usr/src/sys/i386/include perl @/kern/makeops.pl -h @/kern/device_if.m perl @/kern/makeops.pl -h @/kern/bus_if.m perl @/kern/makeops.pl -h @/pci/pci_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr...

...all, i've to encode voice from a voicemodem. I choose speex 1.0.5 for its quality in voice encoding. I've tried to implement an encoder but unsuccesfully. Here's my code: /* ============ SPEEX stream ENCODER ============================================ */ int SPEEX_EncodePCM(struct _IDA_ClientSocket *IDA,char *buffer,unsigned char *PCM,int num_samples) { /* buffer point to the output buffer PCM point to the numsamples bytes 8bit - 8Khz PCM from the modem num_samples is, commonly, 16000 */ int ret,c,d; short int PCM_F[160]; for(c=0;c<num_samples;c++) { /* tempbuf...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've just cvsupped my RELENG_4 tree this morning, and this is what I get when I do make depend after I configure my kernel: mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ - -I@/../include -I/usr/include /usr/src/sys/modules/ida/../../dev/ida/ida.c /usr/src/sys/modules/ida/../../dev/ida/ida_disk.c /usr/src/sys/modules/ida/../../dev/ida/ida_pci.c /usr/src/sys/modules/ida/../../dev/ida/ida_eisa.c/usr/src/sys/modules/ida/../.. /dev/ida/ida.c:41: pci.h: No such file or directory - ------ Vlad Galu Network & Systems Admin...

...ainc.com> wrote: > Fixup patch, addressing Andrew's review feedback: Looks reasonable. > lib/idr.c | 38 +++++++++++++++++++++----------------- I still don't think it should be in this file. You say that some as-yet-unmerged patches will tie the new code into the old ida code. But will it do it in a manner which requires that the two reside in the same file?

...ainc.com> wrote: > Fixup patch, addressing Andrew's review feedback: Looks reasonable. > lib/idr.c | 38 +++++++++++++++++++++----------------- I still don't think it should be in this file. You say that some as-yet-unmerged patches will tie the new code into the old ida code. But will it do it in a manner which requires that the two reside in the same file?

...> > Looks reasonable. > > > > > lib/idr.c | 38 +++++++++++++++++++++----------------- > > > > I still don't think it should be in this file. > > > > You say that some as-yet-unmerged patches will tie the new code into > > the old ida code. But will it do it in a manner which requires that > > the two reside in the same file? > > Not require, no - but it's just intimate enough with my ida rewrite that > I think it makes sense; it makes some use of stuff that should be > internal to the ida code. > &gt...

...> > Looks reasonable. > > > > > lib/idr.c | 38 +++++++++++++++++++++----------------- > > > > I still don't think it should be in this file. > > > > You say that some as-yet-unmerged patches will tie the new code into > > the old ida code. But will it do it in a manner which requires that > > the two reside in the same file? > > Not require, no - but it's just intimate enough with my ida rewrite that > I think it makes sense; it makes some use of stuff that should be > internal to the ida code. > &gt...

...responding cores in between. I ran into this on our downstream product kernels on both 3.14 and 4.1 based kernels, and should apply to the latest kernel as well. Patches can be picked up independently through the respective trees. regards Suman Suman Anna (2): virtio: fix memory leak of virtio ida cache layers remoteproc: fix memory leak of remoteproc ida cache layers drivers/remoteproc/remoteproc_core.c | 2 ++ drivers/virtio/virtio.c | 1 + 2 files changed, 3 insertions(+) -- 2.5.0

...responding cores in between. I ran into this on our downstream product kernels on both 3.14 and 4.1 based kernels, and should apply to the latest kernel as well. Patches can be picked up independently through the respective trees. regards Suman Suman Anna (2): virtio: fix memory leak of virtio ida cache layers remoteproc: fix memory leak of remoteproc ida cache layers drivers/remoteproc/remoteproc_core.c | 2 ++ drivers/virtio/virtio.c | 1 + 2 files changed, 3 insertions(+) -- 2.5.0

..., I''m doing one emergencial migrate for one very old machine, because we will have one IMPLOSION (!!!) very close from here, and I''m thinking that this old IDE disk will not survive... :-/ [root@registro-2 /root]# df -h Filesystem Size Used Avail Use% Mounted on /dev/ida/c0d0p2 3.8G 2.3G 1.4G 62% / /dev/ida/c0d0p8 26G 20G 4.4G 82% /data /dev/ida/c0d0p6 984M 128k 934M 0% /tmp /dev/ida/c0d0p7 984M 166M 768M 18% /var Red Hat Linux release 6.2 (Zoot) Kernel 2.4.16 on a 4-processor i686 I did one copy with ''dd''...

...gt; > > > > > lib/idr.c | 38 +++++++++++++++++++++----------------- > > > > > > I still don't think it should be in this file. > > > > > > You say that some as-yet-unmerged patches will tie the new code into > > > the old ida code. But will it do it in a manner which requires that > > > the two reside in the same file? > > > > Not require, no - but it's just intimate enough with my ida rewrite that > > I think it makes sense; it makes some use of stuff that should be > > internal t...

On Wed, Sep 16, 2015 at 07:29:17PM -0500, Suman Anna wrote: > The virtio core uses a static ida named virtio_index_ida for > assigning index numbers to virtio devices during registration. > The ida core may allocate some internal idr cache layers and > an ida bitmap upon any ida allocation, and all these layers are > truely freed only upon the ida destruction. The virtio_index_ida...

On Wed, Sep 16, 2015 at 07:29:17PM -0500, Suman Anna wrote: > The virtio core uses a static ida named virtio_index_ida for > assigning index numbers to virtio devices during registration. > The ida core may allocate some internal idr cache layers and > an ida bitmap upon any ida allocation, and all these layers are > truely freed only upon the ida destruction. The virtio_index_ida...

...sing Andrew's review feedback: > > Looks reasonable. > > > lib/idr.c | 38 +++++++++++++++++++++----------------- > > I still don't think it should be in this file. > > You say that some as-yet-unmerged patches will tie the new code into > the old ida code. But will it do it in a manner which requires that > the two reside in the same file? Not require, no - but it's just intimate enough with my ida rewrite that I think it makes sense; it makes some use of stuff that should be internal to the ida code. Mostly just sharing the lock thou...

On Thu, Sep 17, 2015 at 07:15:44AM -0700, James Bottomley wrote: > On Thu, 2015-09-17 at 08:33 +0300, Michael S. Tsirkin wrote: > > On Wed, Sep 16, 2015 at 07:29:17PM -0500, Suman Anna wrote: > > > The virtio core uses a static ida named virtio_index_ida for > > > assigning index numbers to virtio devices during registration. > > > The ida core may allocate some internal idr cache layers and > > > an ida bitmap upon any ida allocation, and all these layers are > > > truely freed only upon t...

Hi, i'm following encoder example in the manual.pdf of speex documentation. Here's my portion of code: int SPEEX_EncodePCM(struct _IDA_ClientSocket *IDA,char *buffer,unsigned char *PCM,int num_samples) { int ret,c,d=0,nbBytes,ttBytes=0; float PCM_F[160]; char cBits[200]; #ifndef DISABLESPEEX speex_bits_reset(&IDA->speex_bits); for(c=0;c<num_samples;c++) { PCM_F[d] = (float)((int)PCM[c] << 8) -...

Hi, i'm following encoder example in the manual.pdf of speex documentation. Here's my portion of code: int SPEEX_EncodePCM(struct _IDA_ClientSocket *IDA,char *buffer,unsigned char *PCM,int num_samples) { int ret,c,d=0,nbBytes,ttBytes=0; float PCM_F[160]; char cBits[200]; #ifndef DISABLESPEEX speex_bits_reset(&IDA->speex_bits); for(c=0;c<num_samples;c++) { PCM_F[d] = (float)((int)PCM[c] << 8) -...

The remoteproc core uses a static ida named rproc_dev_index for assigning an automatic index number to a registered remoteproc. The ida core may allocate some internal idr cache layers and ida bitmap upon any ida allocation, and all these layers are truely freed only upon the ida destruction. The rproc_dev_index ida is not destroyed at...

The virtio core uses a static ida named virtio_index_ida for assigning index numbers to virtio devices during registration. The ida core may allocate some internal idr cache layers and an ida bitmap upon any ida allocation, and all these layers are truely freed only upon the ida destruction. The virtio_index_ida is not destroyed at...