search for: 64kbytes

Displaying 20 results from an estimated 21 matches for "64kbytes".

Did you mean: 4kbytes
2002 Sep 11
1
Suggest Rsync Performance Improvements
...essed all the time use valloc() which is memalign(sysconf(_SC_PAGESIZE),size) It aligns memory to the page, so memory copies are word/page align and therefore faster, ie. 4 bytes are copied at once instead of a byte at once. 4. If you use GigaBit ethernet to get performance you need to read/write 64Kbytes to the socket and let the OS break it up into MTU sized packets, or better even send 1Mbytes to the socket. I would change the rsync code, but could not find any into on the variables, so that I could safely change the code, and known it still works. Damon. http://mobile.yahoo.com.au - Yahoo! M...
2008 Jan 14
5
Question about buffering with icecast protocol
Hi, I?ve seen that shoutCAST sends data much faster than real time when you connect (for a while I assume, otherwise you?d be travelling to the future:). That?s useful for fast buffering. With icecast I don?t get that behavior, stream downloads at real time. Is there a way to buffer data faster than real time? Maybe a ?seek? feature? I need that because I need to allocate a special large
2005 Mar 09
2
encoder->server->listener lag
We're running a setup with M3W on a PC in Sri Lanka, encoding to a server in the UK. What factors govern the time delay between things being said to the microphone in SL and heard by a client connecting to the server, and how can we reduce it as much as possible? Currently we're experiencing 20-30 secs or more.
2005 Mar 09
0
encoder->server->listener lag
...n things > being said to the microphone in SL and heard by a client connecting to > the server, and how can we reduce it as much as possible? Currently > we're experiencing 20-30 secs or more. The main 2 factors (which are related) are the prebuffer size of the listening client (eg 64kbytes) and the burst size in icecast (which is used to fill the clients prebuffer quickly). Reduce them both to the smallest you think you can get away with. For example a burst-size 0 and client prebuffer 8 kbytes will mean icecast starts the listener at the latest data received and the client will onl...
2008 Jan 14
1
Question about buffering with icecast protocol
...> With icecast I don?t get that behavior, stream downloads at real time. > Is there a way to buffer data faster than real time? Maybe a ?seek? > feature? I need that because I need to allocate a special large buffer > for an app. Thanks! Look at the burst-size option. The default is 64kbytes which is fine for most audio apps pre-buffering settings but you can alter it to something larger or smaller. To make it similar to shoutcast you'd need to have a burst size of something like 1-2Meg (not sure of the exact figure). karl. No virus found in this incoming message. Checked...
2002 Dec 19
1
Root-NFS not mounting using PXELinux - error 101
...ion. eth0: Intel(R) PRO/1000 Network Connection eth1: Intel(R) PRO/1000 Network Connection SCSI subsystem driver Rev Network driver is loading. Then the thing just won't hook up. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 8192 buckets, 64Kbytes TCP: Hash tables configured (established 262144 bind 65536) GRE over IPv4 tunneling driver NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Looking up port of RPC 100003/2 on 192.168.102.150 RPC: sendmsg returned error 101 portmap: RPC call returned error 101 Root-NFS: Unable to get nfsd port nu...
2005 Feb 16
4
Icecast2 Burst-on-Connect
Can anyone explain what the fundamental difference between the Burst-on-Connect mode that Icecast2 uses versus SHOUTcast? There is a thread starting on the VLC Player list that is stating that the problems that VLC has playing Icecast2 Burst-on-Connect (default) streams is the fault of Icecast2. I don't believe this is true, as Winamp has no problem with Icecast2 streams. I'm hoping
2013 May 12
2
Reinstalling boot blocks on a ZFS-only system
So, I've long known and it makes sense that when you're booted from a ZFS volume, you can't mess with the boot-loader. And, I know a few months ago I had a set of commands I would use when booted from a CD that would initialize the network and copy the "release/boot" from somewhere else so that I could install bootblocks and boot-loaders from more recent code. Sadly, I
2010 Jul 25
4
zpool destroy causes panic
I'm trying to destroy a zfs array which I recently created. It contains nothing of value. # zpool status pool: storage state: ONLINE status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'.
2003 May 06
1
Slow disk access on Dell Latitute with ATA/ATAPI-5 T13 1321D
...sks of 4096K size 1024 blocksize ide-floppy driver 0.99.newide md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 8192 buckets, 64Kbytes TCP: Hash tables configured (established 262144 bind 65536) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 126k freed VFS: Mounted root (ext2 filesystem). Journalled Block Device driver...
2005 Oct 11
0
AW: Re: xen 3.0 boot problem
...device sdj: drive cache: write through > > [ 69.145044] SCSI device sdj: 2097152 512-byte hdwr > > sectors (1074 MB) > > [ 69.145640] SCSI device sdj: drive cache: write through > > [ 69.145780] sdj:<6>IP: routing cache hash table of > > 8192 buckets, 64Kbytes > > [ 69.150433] TCP established hash table entries: > > 131072 (order: 8, 1048576 bytes) > > [ 69.151333] TCP bind hash table entries: 65536 > > (order: 7, 524288 bytes) > > [ 69.151870] TCP: Hash tables configured (established > > 131072 bind 65536)...
2005 Oct 11
0
AW: Re: xen 3.0 boot problem
...device sdj: drive cache: write through > > [ 69.145044] SCSI device sdj: 2097152 512-byte hdwr > > sectors (1074 MB) > > [ 69.145640] SCSI device sdj: drive cache: write through > > [ 69.145780] sdj:<6>IP: routing cache hash table of > > 8192 buckets, 64Kbytes > > [ 69.150433] TCP established hash table entries: > > 131072 (order: 8, 1048576 bytes) > > [ 69.151333] TCP bind hash table entries: 65536 > > (order: 7, 524288 bytes) > > [ 69.151870] TCP: Hash tables configured (established > > 131072 bind 65536)...
2014 Jun 11
2
Re: libguestfs supermin error
...version > 4.1.0 > [ 1.061434] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd. > [ 1.064252] xt_time: kernel timezone is -0000 > [ 1.065602] IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP) > [ 1.067159] IPVS: Connection hash table configured (size=4096, > memory=64Kbytes) > [ 1.069253] IPVS: Creating netns size=2024 id=0 > [ 1.070459] IPVS: ipvs loaded. > [ 1.071183] IPVS: [rr] scheduler registered. > [ 1.072265] IPVS: [wrr] scheduler registered. > [ 1.073429] IPVS: [lc] scheduler registered. > [ 1.074528] IPVS: [wlc] scheduler r...
2014 Jun 10
2
Re: libguestfs supermin error
Hi Rich I'm able to solve the problem regarding PAPR in libguestfs on my powerpc ubuntu.By default the libguestfs was configuring pseries machine and afterwards I changed it to my original machine i.e ppce500 .The changes are performed in ./src/guestfs-internal.h file. Thanks On Tue, Jun 10, 2014 at 7:58 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Wed, Jun 04, 2014 at
2018 Jul 26
2
net-next boot error
...ntrack_irc: failed to register helpers > nf_conntrack_sane: failed to register helpers > nf_conntrack_sip: failed to register helpers > xt_time: kernel timezone is -0000 > IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP) > IPVS: Connection hash table configured (size=4096, memory=64Kbytes) > IPVS: ipvs loaded. > IPVS: [rr] scheduler registered. > IPVS: [wrr] scheduler registered. > IPVS: [lc] scheduler registered. > IPVS: [wlc] scheduler registered. > IPVS: [fo] scheduler registered. > IPVS: [ovf] scheduler registered. > IPVS: [lblc] scheduler registered. &gt...
2018 Jul 26
2
net-next boot error
...ntrack_irc: failed to register helpers > nf_conntrack_sane: failed to register helpers > nf_conntrack_sip: failed to register helpers > xt_time: kernel timezone is -0000 > IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP) > IPVS: Connection hash table configured (size=4096, memory=64Kbytes) > IPVS: ipvs loaded. > IPVS: [rr] scheduler registered. > IPVS: [wrr] scheduler registered. > IPVS: [lc] scheduler registered. > IPVS: [wlc] scheduler registered. > IPVS: [fo] scheduler registered. > IPVS: [ovf] scheduler registered. > IPVS: [lblc] scheduler registered. &gt...
2005 Nov 25
28
ZFS and memcntl(..., MC_SYNC, ...)
...t. The reason for this is because it''s very slow on UFS for large buffers - effectively linear with the number of pages crossed, or about 6ms per 8KBytes on an otherwise idle SCSI disk on SPARC. The good news is that this is very fast on ZFS - on the same disk, about 7ms constant for up to 64KBytes, and about 20ms constant for 256KBytes. However this is still a bit slower than the msync(3C) approach on UFS] Thanks in advance. -- Philip Beevers mailto:philip.beevers at ntlworld.com
2018 Jul 26
0
net-next boot error
...ister helpers > > nf_conntrack_sane: failed to register helpers > > nf_conntrack_sip: failed to register helpers > > xt_time: kernel timezone is -0000 > > IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP) > > IPVS: Connection hash table configured (size=4096, memory=64Kbytes) > > IPVS: ipvs loaded. > > IPVS: [rr] scheduler registered. > > IPVS: [wrr] scheduler registered. > > IPVS: [lc] scheduler registered. > > IPVS: [wlc] scheduler registered. > > IPVS: [fo] scheduler registered. > > IPVS: [ovf] scheduler registered. > &gt...
2005 Apr 21
10
apci issue
Hi, Updated to current bk today, and my machine stopped booting ... I''ve tracked it down to the apic changes from end of last week. cset 1.1307 boots fine, 1.1308 doesn''t. Diff of the boot messages is below. Full logs are also attached. Gerd --- log-1.1307 2005-04-21 14:40:57.372885027 +0200 +++ log-1.1308 2005-04-21 14:38:52.236553392 +0200 @@ -7,7 +7,7 @@
2012 Jan 12
9
linux 3.3-pre-rc1: Starting domU fails with Error: Failed to query current memory allocation of dom0.
Hi Konrad, Today i tried linuses tree of today (last commit is 4c4d285ad5665bfbd983b95fde8d7a477d24a361). It boots dom0 fine, but it fails to start any domU with: "Error: Failed to query current memory allocation of dom0." With my previous 3.1.5 kernel everything is fine, nothing else changed in config in between. dmesg and xm dmesg attached -- Sander Dom0 shows: total