search for: emptions

...r), it's slightly cleaner if we instead declare that we are already blocked. I tested with: $ nbdkit -U - null 16M --run 'examples/threaded-reads-and-writes $unixsocket' There was no real noticeable difference in timing, but I did observe that pre-patch, the run encountered 168825 pre-emptions and 136976 send() EAGAIN failures (81%), while post-patch the run encountered 166066 pre-emptions and 552 EAGAIN failures (0.3%). --- generator/states-issue-command.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/generator/states-issue-command.c b/generator/states...

Besides playing with Asterisk, i'm also using Linux for all kinds of multimedia things, especially recording music, mixing, etc. In order to use Linux as a digital audio workstation, there are a few things that one must do: use low-latency kernels, use pre-emption, use apps that run with real-time privileges, etc. For example, among audio Linux users, the CK (Con Kolivas) and LCK (Locosoft

...> instead declare that we are already blocked. > > I tested with: > $ nbdkit -U - null 16M --run 'examples/threaded-reads-and-writes $unixsocket' > > There was no real noticeable difference in timing, but I did observe > that pre-patch, the run encountered 168825 pre-emptions and 136976 > send() EAGAIN failures (81%), while post-patch the run encountered > 166066 pre-emptions and 552 EAGAIN failures (0.3%). > --- > generator/states-issue-command.c | 11 ++++++++--- > 1 file changed, 8 insertions(+), 3 deletions(-) > > diff --git a/generator/states...

When processing a server reply within the REPLY subgroup, we will often hit a situation where recv() requires us to block until the next NotifyRead. But since NotifyRead is the only permitted external action while in this group, we are effectively blocking CmdIssue and NotifyWrite events from happening until the server finishes the in-progress reply, even though those events have no strict

Olaf Hopp <Olaf.Hopp at kit.edu> writes: > I have dovecot shielded by fail2ban which works fine. But since a few > days I see many many IPs per day knocking on my doors with wron > password and/or users. But the rate at which they are knocking is very > very low. So fail2ban will never catch them. Slow roll distributed attacks. Really hard to stop. > And I see many many

From what I see on their descriptions (site is in Chinese!), this is NOT a replacement of WINE. They place certain system services in the kernel and have compile kernel-module (.ko) to service them. The kernel patches are very small so this is not "bloat" as someone has stated. My main question is how such patches effect OTHER common patches, especially real-time pre-emption. If

We have setup asterisk to handle our calls before between telco and an Avaya definity. The PRI keeps locking up every so often. In addition I keep getting this error when trying to call the avaya: -- Channel 0/2, span 1 got hangup request, cause 102 -- Hungup 'Zap/2-1' When that error happens I get a fast busy (congestion) tone. Any one can point me in the right direction? TIA

Keywords T1 Q.931 isdn disconnect cause codes itu standard libpri Dont know if anyone wondered what q.931 cause codes are but i wishwe could get these back into the dial plan as a var Standard Q931 Codes Decimal Value Hexadecimal Value Definition 1 01 Unallocated (unassigned) number. This number is not in the routing table or it has no path across the ISDN cloud (network). 1. Check routing

Hello all, As some of you may already know from comments in the GitHub pull requests and other media, due to pre-emption by real life our long-term leader and main maintainer, Arnaud Quette, had to step down from this role and from intensive involvement in the NUT project (we hope he would still be able to help on occasion, time permitting). He asked the members of the core team to take over,

Hello all, As some of you may already know from comments in the GitHub pull requests and other media, due to pre-emption by real life our long-term leader and main maintainer, Arnaud Quette, had to step down from this role and from intensive involvement in the NUT project (we hope he would still be able to help on occasion, time permitting). He asked the members of the core team to take over,

On Fri, 02 Oct 2009 00:07:07 +0100 Stuart Bennett <stuart at freedesktop.org> wrote: > Pekka Paalanen wrote: > > Hi Stuart, > > > > I'm not sure you know, but annarchy just lost all user homes. > > Could you push vbtracetool and whatever personal git repos you > > had, so we can clone them? > > Hey Pekka, I've re-upped vbtracetool and

Hi, questions will follow. --- diff --git a/drivers/gpu/drm/nouveau/nouveau_bios.c b/drivers/gpu/drm/nouveau/nouveau_bios.c index 99f7bd4..13b3fb1 100644 --- a/drivers/gpu/drm/nouveau/nouveau_bios.c +++ b/drivers/gpu/drm/nouveau/nouveau_bios.c @@ -40,8 +40,6 @@ #define BIOSLOG(sip, fmt, arg...) NV_DEBUG(sip->dev, fmt, ##arg) #define LOG_OLD_VALUE(x) //x -#define BIOS_USLEEP(n)

I recently sent off a fix for lazy vmalloc faults which can happen under = paravirt when lazy mode is enabled. Unfortunately, I jumped the gun a = bit on fixing this. I neglected to notice that since the new call to = flush the MMU update queue is called from the page fault handler, it can = be pre-empted. Both VMI and Xen use per-cpu variables to track lazy = mode state, as all previous

I recently sent off a fix for lazy vmalloc faults which can happen under = paravirt when lazy mode is enabled. Unfortunately, I jumped the gun a = bit on fixing this. I neglected to notice that since the new call to = flush the MMU update queue is called from the page fault handler, it can = be pre-empted. Both VMI and Xen use per-cpu variables to track lazy = mode state, as all previous

What are methods to debug domU when it hangs? Using xen 3.1 compiled from sources I could not manage to launch no domU. Fot instance, I run something like this: =====8<===================== disk = [ ''file:/oradata-act/sles.disk,hda1,w'', '',hdc:cdrom,r'' ] kernel = "/boot/vmlinuz-2.6.18-xen" ramdisk = "/boot/initrd-2.6.18-xen" cpus =

IA-32 linear address translation is loads of fun. While cleaning up the LDT code, I noticed that kprobes code was very bogus with respect to segment handling. Many, many bugs are fixed here. I chose to combine the three separate functions that try to do linear address conversion into one, nice and working functions. All of the versions had bugs. 1) Taking an int3 from v8086 mode could cause

IA-32 linear address translation is loads of fun. While cleaning up the LDT code, I noticed that kprobes code was very bogus with respect to segment handling. Many, many bugs are fixed here. I chose to combine the three separate functions that try to do linear address conversion into one, nice and working functions. All of the versions had bugs. 1) Taking an int3 from v8086 mode could cause

Hello, find enclosed a first patch for adding tail call optimizations for thumb1 targets. I assume that this list is the right place for publishing patches for review? Since this is my first proposal for LLVM, I'd very much appreciate your feedback. What the patch is meant to do: For Tail calls identified during DAG generation, the target address will be loaded into a register by use

Folks, Please find attached a proposal for the Xen development roadmap for the next 18 months or so. The roadmap gives a "state of the nation" summary and provides suggestions as to priorities going forward. I''ve tried to be inclusive and collect together many of the various features that folks have asked for, along with some implementation ideas to guide developers. The