similar to: hmm uploading?

>Joris Vandeweerd wrote: > > you can watch on my site www.kayalion.net with network usage, eth1 is >the > > internet. > > > > i rebooted my server last night. i didn't connect and watched my eth1, >after > > 10 minutes there was allready +-8mb sent. > > stats now: > > uptime : 14 hours 20 minutes > > network usage : 736.02 MB > >

hello, i got a question. is it possible that if there aren't any listeners my radio is still sending the music to the internet?? i thought he didnt do this used to be, but when i'm looking at my network usage it keepos sending. first i thought it was because my ices connects to my icecast using kayalion.homelinux.net (internet) but when i connect ices through lan it still keeps

yeah, tnx very much, i think the problem is solved now, i thought idd it was something with the mp3's but i didn't knew what. >Hi: > >Well, I've tuned in and not struck the problem as yet. But I'm guessing >that the problem is that the problematic songs aren't at the same sampling >rate. The three songs I've heard so far are at 32kbps 11.025khz stereo.

-------- Original Message -------- Subject: DGA (/dev/mem) Date: Wed, 12 Dec 2001 21:32:07 +0000 From: "Mark Hannessen" <msh104@hotmail.com> To: wwn@winehq.com Hee wine guys. I have been using wine for a while now and i think it is generely a good idea ( much better than having boot your entire windows operating system inside linux ) It is a shame it is a little unstable

hello, i've setup an icecast server v 1.3.12 with ices 0.2.3. when a certain song begins, you don't get any sound from that song and the song after. First it was with just 5 songs but now he does it more and more. when i look at my page i'm still connected. when i got the silence and reconnect, i get the song. desperate i tried shout and he does it to + more buffering :(. my mp3's

How exactly is LMTP proxying supposed to work? According to the example on http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy I'm only seeing "proxy" in the password_query statements. But LMTP never sends a password. IMAP Proxying is working OK: Sep 24 12:51:09 imap-login: Info: proxy(ralf.hildebrandt at charite.de): started proxying to dovecot.charite.de:993:

Reviewed-by: Christoph Hellwig <hch at lst.de>

From: Jason Gunthorpe <jgg at mellanox.com> There is no reason for a user to select this or not directly - it should be selected by drivers that are going to use the feature, similar to how CONFIG_HMM_MIRROR works. Currently all drivers provide a feature kconfig that will disable use of DEVICE_PRIVATE in that driver, allowing users to avoid enabling this if they don't want the

From: Jason Gunthorpe <jgg at mellanox.com> There is no reason for a user to select this or not directly - it should be selected by drivers that are going to use the feature, similar to how CONFIG_HMM_MIRROR works. Currently all drivers provide a feature kconfig that will disable use of DEVICE_PRIVATE in that driver, allowing users to avoid enabling this if they don't want the

On Wed, Apr 22, 2020 at 08:03:29AM +0200, Christoph Hellwig wrote: > > > On Tue, Apr 21, 2020 at 09:21:46PM -0300, Jason Gunthorpe wrote: > > +void nouveau_hmm_convert_pfn(struct nouveau_drm *drm, struct hmm_range *range, > > + u64 *ioctl_addr) > > { > > unsigned long i, npages; > > > > + /* > > + * The ioctl_addr prepared here is

On Fri, 1 May 2020 15:20:44 -0300 Jason Gunthorpe <jgg at ziepe.ca> wrote: > From: Jason Gunthorpe <jgg at mellanox.com> > > There is no reason for a user to select this or not directly - it should > be selected by drivers that are going to use the feature, similar to how > CONFIG_HMM_MIRROR works. > > Currently all drivers provide a feature kconfig that will

From: Jason Gunthorpe <jgg at mellanox.com> This is just an alias for HMM_PFN_ERROR, nothing cares that the error was because of a special page vs any other error case. Signed-off-by: Jason Gunthorpe <jgg at mellanox.com> --- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 1 - drivers/gpu/drm/nouveau/nouveau_svm.c | 1 - include/linux/hmm.h | 8 -------- mm/hmm.c

From: Jason Gunthorpe <jgg at mellanox.com> This is just an alias for HMM_PFN_ERROR, nothing cares that the error was because of a special page vs any other error case. Acked-by: Felix Kuehling <Felix.Kuehling at amd.com> Reviewed-by: Christoph Hellwig <hch at lst.de> Signed-off-by: Jason Gunthorpe <jgg at mellanox.com> --- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 1 -

From: Jason Gunthorpe <jgg at mellanox.com> Only the function calls are stubbed out with static inlines that always fail. This is the standard way to write a header for an optional component and makes it easier for drivers that only optionally need HMM_MIRROR. Reviewed-by: J?r?me Glisse <jglisse at redhat.com> Tested-by: Ralph Campbell <rcampbell at nvidia.com> Signed-off-by:

On 5/1/20 11:20 AM, Jason Gunthorpe wrote: > From: Jason Gunthorpe <jgg at mellanox.com> > > Presumably the intent here was that hmm_range_fault() could put the data > into some HW specific format and thus avoid some work. However, nothing > actually does that, and it isn't clear how anything actually could do that > as hmm_range_fault() provides CPU addresses which

On Tue, Apr 21, 2020 at 09:21:43PM -0300, Jason Gunthorpe wrote: > From: Jason Gunthorpe <jgg at mellanox.com> > > hmm_vma_walk->last is supposed to be updated after every write to the > pfns, so that it can be returned by hmm_range_fault(). However, this is > not done consistently. Fortunately nothing checks the return code of > hmm_range_fault() for anything other

On Tue, Apr 21, 2020 at 09:21:46PM -0300, Jason Gunthorpe wrote: > +void nouveau_hmm_convert_pfn(struct nouveau_drm *drm, struct hmm_range *range, > + u64 *ioctl_addr) > { > unsigned long i, npages; > > + /* > + * The ioctl_addr prepared here is passed through nvif_object_ioctl() > + * to an eventual DMA map on some call chain like: > + *

From: Jason Gunthorpe <jgg at mellanox.com> hmm_vma_walk->last is supposed to be updated after every write to the pfns, so that it can be returned by hmm_range_fault(). However, this is not done consistently. Fortunately nothing checks the return code of hmm_range_fault() for anything other than error. More importantly last must be set before returning -EBUSY as it is used to prevent

From: Jason Gunthorpe <jgg at mellanox.com> hmm_vma_walk->last is supposed to be updated after every write to the pfns, so that it can be returned by hmm_range_fault(). However, this is not done consistently. Fortunately nothing checks the return code of hmm_range_fault() for anything other than error. More importantly last must be set before returning -EBUSY as it is used to prevent

Hello All. Is mod_php for apache hiding in a repo somewhere? I did a yum --enablerepo=centosplus install mod_php (as googled) but I don't see any mod_php lurking anywhere. Anyone know what's up? Thanks -- Flambeau Inc. Technology Center - Baraboo, WI Email : tblader at flambeau.com Keyserver: http://pgp.mit.edu KeyID: 0x00E9EC2C