search for: unthrottled

Hi; I'm looking for CentOS 5.0 x86_64 dvd iso (preferably not torrent); must be 5.0 All my web searches have come up with more recent versions of 5.x, not 5.0. Can someone give me a URL I can wget with? I'd even be willing to throttle down the wget). Thanks, Ken Wolcott

Hi All, I''m trying to do something regarding Bandwith Aggregation and I would need to set new options in the IP-header. I had been studying some kernel source that concern to the IP layer, but I don''t really know how to set a new option. Does anyone have any idea to add new custom options into the IP header ? Thank you in advance Felipe Herrera

I am doing some benchmarking of rsync. I am using the --bwlimit= option to throttle down rsync to predict its operation over slow communications links. I am using rsync 2.6.2 from the release site without any patches. I downloaded the release rather than pull from the CVS tree. I have 2 servers "wilber" (the remote archive) and "judy" (the local archive) connected with a gig

...s correctly rate limited to 1 MBps or less. With a >> short queue, it ends up dropping a lot and sending even less. >> >> When a queue builds up for sender B, sender A throughput is strongly >> correlated with queue length. With queue length 1, it can send almost >> at unthrottled speed. But even at limit 100 its throughput is on the >> same order as sender B. >> >> What is surprising to me is that this happens even though the number >> of ubuf_info in use at limit 100 is around 100 at all times. In other words, >> it does not exhaust the pool....

...s correctly rate limited to 1 MBps or less. With a >> short queue, it ends up dropping a lot and sending even less. >> >> When a queue builds up for sender B, sender A throughput is strongly >> correlated with queue length. With queue length 1, it can send almost >> at unthrottled speed. But even at limit 100 its throughput is on the >> same order as sender B. >> >> What is surprising to me is that this happens even though the number >> of ubuf_info in use at limit 100 is around 100 at all times. In other words, >> it does not exhaust the pool....

...might become an issue though. Another option might be to just scale the cursor as well. If I understand correctly the "cursor can't be scaled" limitation just comes from the fact that some vblank synced resource needs to be reconfigured whenever the scaling changes. So doing that for unthrottled cursor updates is not easy. But in this case the underscan properties are what determines the scaling so maybe that resource could be reconfigured whenever the those props change to make sure the cursor can always be scaled appropriately? > > Anyway, I'd like to hear back from Eric on t...

...ited to 1 MBps or less. With a >>> short queue, it ends up dropping a lot and sending even less. >>> >>> When a queue builds up for sender B, sender A throughput is strongly >>> correlated with queue length. With queue length 1, it can send almost >>> at unthrottled speed. But even at limit 100 its throughput is on the >>> same order as sender B. >>> >>> What is surprising to me is that this happens even though the number >>> of ubuf_info in use at limit 100 is around 100 at all times. In other >>> words, >>&g...

...ream linking to ? prevent a compile issue. - lib-storage: Mailbox synchronization may have assert-crashed in some ? rare situations. - lib-storage: mdbox didn't preserve date.saved with dsync. - lib: Don't require EAI_{ADDRFAMILY,NODATA}, breaks FreeBSD - master: Some services could respawn unthrottled if they crash during ? startup. - push-notification: Do not send push_notification_finished event if ? nothing was done. This happens when mail transaction is started and ? ended with no changes. - quota-status: Addresses with special characters in the local part caused ? problems in the interactio...

...ream linking to ? prevent a compile issue. - lib-storage: Mailbox synchronization may have assert-crashed in some ? rare situations. - lib-storage: mdbox didn't preserve date.saved with dsync. - lib: Don't require EAI_{ADDRFAMILY,NODATA}, breaks FreeBSD - master: Some services could respawn unthrottled if they crash during ? startup. - push-notification: Do not send push_notification_finished event if ? nothing was done. This happens when mail transaction is started and ? ended with no changes. - quota-status: Addresses with special characters in the local part caused ? problems in the interactio...

...s/intel_audio_dump: add support for Broxton Maarten Lankhorst (1): tests/kms_setmode: Handle MST correctly. Marius Vlad (1): tests/pm_rpm tests for set_caching and set_tiling ioctl(s) Matt Roper (2): kms_universal_plane: Add gen9-specific test kms_cursor_crc: Add test for unthrottled cursor movement Matt Turner (1): tools/aubdump: Link with -ldl. Mika Kuoppala (2): lib: Add Skylake Intel Graphics GT4 PCI IDs tests/drm_import_export: Always loop with mutex held Paulo Zanoni (19): lib/igt_fb: don't forget to close parens on message printed kms...

...tive I evaluated was using a single "stop for some > time" message with an exponential or fibonacci backoff with a ceiling, > but the downside is that a congested queue could block the "stop" > message from reaching the source and eventually the source would become > unthrottled even though the destination is *trying* to throttle it. I > think this is bad for some pretty abusable cases, such as creating a > socket that has no receiver. A stop/start message pair doesn't have this > issue. > > > > > > > > > + > > > > >...

...tive I evaluated was using a single "stop for some > time" message with an exponential or fibonacci backoff with a ceiling, > but the downside is that a congested queue could block the "stop" > message from reaching the source and eventually the source would become > unthrottled even though the destination is *trying* to throttle it. I > think this is bad for some pretty abusable cases, such as creating a > socket that has no receiver. A stop/start message pair doesn't have this > issue. > > > > > > > > > + > > > > >...

...t;stop for some > > > time" message with an exponential or fibonacci backoff with a ceiling, > > > but the downside is that a congested queue could block the "stop" > > > message from reaching the source and eventually the source would become > > > unthrottled even though the destination is *trying* to throttle it. I > > > think this is bad for some pretty abusable cases, such as creating a > > > socket that has no receiver. A stop/start message pair doesn't have this > > > issue. > > > > > > > > &g...

On Fri, May 11, 2018 at 07:12:21PM +0200, Boris Brezillon wrote: > On Fri, 11 May 2018 19:54:02 +0300 > Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > > > On Fri, May 11, 2018 at 05:52:56PM +0200, Boris Brezillon wrote: > > > On Fri, 11 May 2018 18:34:50 +0300 > > > Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > > >

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual