search for: syncrhonize

...spinlock synchronize MMU notifier with accessors >> >> Changes from V3: >> - remove the unnecessary patch >> >> Changes from V2: >> - use seqlck helper to synchronize MMU notifier with vhost worker >> >> Changes from V1: >> - try not use RCU to syncrhonize MMU notifier with vhost worker >> - set dirty pages after no readers >> - return -EAGAIN only when we find the range is overlapped with >> metadata >> >> Jason Wang (9): >> vhost: don't set uaddr for invalid address >> vhost: validate MMU notif...

...spinlock synchronize MMU notifier with accessors >> >> Changes from V3: >> - remove the unnecessary patch >> >> Changes from V2: >> - use seqlck helper to synchronize MMU notifier with vhost worker >> >> Changes from V1: >> - try not use RCU to syncrhonize MMU notifier with vhost worker >> - set dirty pages after no readers >> - return -EAGAIN only when we find the range is overlapped with >> metadata >> >> Jason Wang (9): >> vhost: don't set uaddr for invalid address >> vhost: validate MMU notif...

...m V3: > > > > - remove the unnecessary patch > > > > > > > > Changes from V2: > > > > - use seqlck helper to synchronize MMU notifier with vhost worker > > > > > > > > Changes from V1: > > > > - try not use RCU to syncrhonize MMU notifier with vhost worker > > > > - set dirty pages after no readers > > > > - return -EAGAIN only when we find the range is overlapped with > > > > metadata > > > > > > > > Jason Wang (9): > > > > vhost: don't...

...m V3: > > > > - remove the unnecessary patch > > > > > > > > Changes from V2: > > > > - use seqlck helper to synchronize MMU notifier with vhost worker > > > > > > > > Changes from V1: > > > > - try not use RCU to syncrhonize MMU notifier with vhost worker > > > > - set dirty pages after no readers > > > > - return -EAGAIN only when we find the range is overlapped with > > > > metadata > > > > > > > > Jason Wang (9): > > > > vhost: don't...

...ges from V4: > - switch to use spinlock synchronize MMU notifier with accessors > > Changes from V3: > - remove the unnecessary patch > > Changes from V2: > - use seqlck helper to synchronize MMU notifier with vhost worker > > Changes from V1: > - try not use RCU to syncrhonize MMU notifier with vhost worker > - set dirty pages after no readers > - return -EAGAIN only when we find the range is overlapped with > metadata > > Jason Wang (9): > vhost: don't set uaddr for invalid address > vhost: validate MMU notifier registration > vhost:...

...t; > > > > Changes from V3: > > > - remove the unnecessary patch > > > > > > Changes from V2: > > > - use seqlck helper to synchronize MMU notifier with vhost worker > > > > > > Changes from V1: > > > - try not use RCU to syncrhonize MMU notifier with vhost worker > > > - set dirty pages after no readers > > > - return -EAGAIN only when we find the range is overlapped with > > > metadata > > > > > > Jason Wang (9): > > > vhost: don't set uaddr for invalid address...

Hi! I have always had problems with the time of my Windows guests, but I didn''t really care about it, because I ran time syncronization software after boot, and everything became normal. Recently we switched to virtualized Active Directory Controllers which makes this an even bigger problem, because time syncrhonization is very important there, and it should be precise right at boot time

...; > > > > > > > Changes from V2: > > > > > > > - use seqlck helper to synchronize MMU notifier with vhost worker > > > > > > > > > > > > > > Changes from V1: > > > > > > > - try not use RCU to syncrhonize MMU notifier with vhost worker > > > > > > > - set dirty pages after no readers > > > > > > > - return -EAGAIN only when we find the range is overlapped with > > > > > > > metadata > > > > > > > > > >...

We recently installed Samba 3.x server on Linux system (RHEL 3.0, using stock RH samba packages). We are observing following messages in logs: lib/access.c:check_access(328) and access is denied. I know why we get access denied: we have restricted "hosts allow =" setting. My question is: why are we getting connection requests in first place? I think something is advertising this

...eta data accelreation series. Please review. Changes from V4: - switch to use spinlock synchronize MMU notifier with accessors Changes from V3: - remove the unnecessary patch Changes from V2: - use seqlck helper to synchronize MMU notifier with vhost worker Changes from V1: - try not use RCU to syncrhonize MMU notifier with vhost worker - set dirty pages after no readers - return -EAGAIN only when we find the range is overlapped with metadata Jason Wang (9): vhost: don't set uaddr for invalid address vhost: validate MMU notifier registration vhost: fix vhost map leak vhost: reset inval...

...eta data accelreation series. Please review. Changes from V4: - switch to use spinlock synchronize MMU notifier with accessors Changes from V3: - remove the unnecessary patch Changes from V2: - use seqlck helper to synchronize MMU notifier with vhost worker Changes from V1: - try not use RCU to syncrhonize MMU notifier with vhost worker - set dirty pages after no readers - return -EAGAIN only when we find the range is overlapped with metadata Jason Wang (9): vhost: don't set uaddr for invalid address vhost: validate MMU notifier registration vhost: fix vhost map leak vhost: reset inval...

...>>>>> - remove the unnecessary patch >>>>> >>>>> Changes from V2: >>>>> - use seqlck helper to synchronize MMU notifier with vhost worker >>>>> >>>>> Changes from V1: >>>>> - try not use RCU to syncrhonize MMU notifier with vhost worker >>>>> - set dirty pages after no readers >>>>> - return -EAGAIN only when we find the range is overlapped with >>>>> metadata >>>>> >>>>> Jason Wang (9): >>>>> vhost: don...

Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. This patch-set follows the main idea discussed at 2012 LSFMMS session: "Ballooning for transparent huge

Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. This patch-set follows the main idea discussed at 2012 LSFMMS session: "Ballooning for transparent huge

Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. This patch-set follows the main idea discussed at 2012 LSFMMS session: "Ballooning for transparent huge

Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. This patch-set follows the main idea discussed at 2012 LSFMMS session: "Ballooning for transparent huge

Hi all: This series try to fix several issues introduced by meta data accelreation series. Please review. Changes from V2: - use seqlck helper to synchronize MMU notifier with vhost worker Changes from V1: - try not use RCU to syncrhonize MMU notifier with vhost worker - set dirty pages after no readers - return -EAGAIN only when we find the range is overlapped with metadata Jason Wang (9): vhost: don't set uaddr for invalid address vhost: validate MMU notifier registration vhost: fix vhost map leak vhost: reset inval...

Hi all: This series try to fix several issues introduced by meta data accelreation series. Please review. Changes from V3: - remove the unnecessary patch Changes from V2: - use seqlck helper to synchronize MMU notifier with vhost worker Changes from V1: - try not use RCU to syncrhonize MMU notifier with vhost worker - set dirty pages after no readers - return -EAGAIN only when we find the range is overlapped with metadata Jason Wang (9): vhost: don't set uaddr for invalid address vhost: validate MMU notifier registration vhost: fix vhost map leak vhost: reset inval...

Hi all: This series try to fix several issues introduced by meta data accelreation series. Please review. Changes from V3: - remove the unnecessary patch Changes from V2: - use seqlck helper to synchronize MMU notifier with vhost worker Changes from V1: - try not use RCU to syncrhonize MMU notifier with vhost worker - set dirty pages after no readers - return -EAGAIN only when we find the range is overlapped with metadata Jason Wang (9): vhost: don't set uaddr for invalid address vhost: validate MMU notifier registration vhost: fix vhost map leak vhost: reset inval...

Memory fragmentation introduced by ballooning might reduce significantly the number of 2MB contiguous memory blocks that can be used within a guest, thus imposing performance penalties associated with the reduced number of transparent huge pages that could be used by the guest workload. This patch-set follows the main idea discussed at 2012 LSFMMS session: "Ballooning for transparent huge