similar to: Setting elevator=noop in the guest necessary?

Can anyone explain how the disk elevator works and if there is anyway to tweak it? I have an email server which likely has a large number of read and write requests and was wandering if there was anyway to improve performance. Matt

Hi! I''m trying to figure out what would be the best io elevator/scheduler for dom0. As far as I know, each domU virtual disk device is seen as single process in dom0.. correct? Then, say, I have domU with 3 devices (sda1,sda2,sda3).. and I access all of those 3 devices in domU.. that would make 3 processes doing io in dom0? elevator=cfg would be a good pick to share the io load

In past on my machines with single drive or software RAID I have always had to change elevator to deadline. Mainly due to fact I was running email server with a great deal of I/O. Switching from CFQ to Deadline made a huge difference. I am wandering if with a hardware RAID controller should I still switch too Deadline or does the RAID controller do reordering etc. for me? Likely best answer is

In case anybody else has found their --noop flag (and probably others) ignored with 24.6 here''s why, and while this may be a known issue I didn''t find it in the discussion board after some searching so wanted to save others.. I can''t remember why it was done, but at some point I made puppetd.conf a symlink to puppet.conf. For whatever reason, this causes the flag to

Hi, I Just setup asterisk to send SIP calls to a SIP redirect server that response back with a list of destinations, if the first destination is not able to terminate the call, asterisk does not try the second , it just hang up. How can I Noop and capture the list inside the 3xx response?, for storing it and then by using Dial status, I will be able of failover through that list and hang-up

2008/11/6 Steve Murphy <murf at digium.com> > On Thu, 2008-11-06 at 13:55 +0100, Olivier wrote: > > > > > Yes, you're right : NoOp needs verbosity of 3 and above. > > Thanks for helping. > > > > The surprising thing is that AEL Verbose prints output whatever the > > verbosity level is (even with 0). > > Would you qualify this as normal ?

The Wikipedia pages about schedulers are quite informative. I don't know _why_ this makes a difference, but it does seem to make a small one. Even though for a single process (guestfsd) it would seem that the choice of scheduler should make no difference. BTW the default scheduler in the guest is 'cfq'. http://en.wikipedia.org/wiki/Noop_scheduler http://en.wikipedia.org/wiki/CFQ

so i confess i'm still not clear on what the first index into getelementptr is all about. it makes perfect sense for an example like getelementptr %mystruct * %reg100 to just return a %mystruct * equivalent to %reg100. it does *not* make sense to me that getelementptr %mystruct * %reg100, uint 0 should act the same. for look, what this speaks of to me is indexing the first element in an

Hi all, i want lock Zap channels via global var FREE1 if FREE1 = 1 then call should go on with nothing and waiting for digits to go in _X. Otherwise hangup the channel But if the GotoIf goes to s|4 (NoOp) then comes a ringing indication.... !? The "immediate" property in the zapat.conf is "yes" [tel1] exten => s,1,GotoIf($[${FREE1} = 1]?s|4:s|2) exten =>

Sometimes I see in a context "NoOp" What is the purpose of "NoOp" (no operation) if it does nothing? -- #Joseph

Hello everyone, I'm trying to send debugging messages to the console. However, although my system seems to be working fine, it does not seem to be printing the NoOp messages on the console... Are there any flags that prevent that to happen? BTW, how to log specific debug messages to a log file? Any suggestions? Thanks for your help, Leo

Hey all, I could have sworn I saw it done once, and it seems to make perfect sense that someone might want to colour code the NoOp() lines so that the console logging messages stand out more. If anyone has done this and wouldn't mind sharing the secret, I'd be much appreciative! Thanks! Leif Madsen.

> > Let me guess: The context in which you have the 2 thru n priorities is > the same one as you're using for regcontext right? > > Don't do that, bad things will happen (as you've noticed). > > I'd have to review the code again, but I think what you're seeing is as > a result of this. > > Regards, > - Brad > No, not exactly, I have a

OK this was an easy one to fix. All I had to do is RTFM. Note on the wiki: ATTENTION: Make sure you take a look at bug report 7144 Just do what Kevin said, include the regcontext in whatever static context you have the priority 2 extension and don't make a static regcontext in extension.conf. Let sip module do the rest. Works great. Thanks Guys. JR On 12/5/06, JR Richardson

Hi, I've new to http://www.voip-info.org/wiki/view/Asterisk+AEL2 I'm using NoOp and Verbose functions inside extensions.ael. Strangely, NoOp is not printing anything in Asterisk console while Verbose is working. Am I missing something obvious ? Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL:

Some of the alpha pci noop dma ops are identical to the common ones. Use them. Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com> --- arch/alpha/kernel/pci-noop.c | 46 ++++---------------------------------------- 1 file changed, 4 insertions(+), 42 deletions(-) diff --git a/arch/alpha/kernel/pci-noop.c b/arch/alpha/kernel/pci-noop.c index 2b1f4a1..8e735b5e 100644 ---

On Fri, Oct 30, 2015 at 02:20:35PM +0100, Christian Borntraeger wrote: > +static void *dma_noop_alloc(struct device *dev, size_t size, > + dma_addr_t *dma_handle, gfp_t gfp, > + struct dma_attrs *attrs) > +{ > + void *ret; > + > + ret = (void *)__get_free_pages(gfp, get_order(size)); > + if (ret) { > + memset(ret, 0, size); There is no need to zero out the

Some of the alpha pci noop dma ops are identical to the common ones. Use them. Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com> Reviewed-by: Joerg Roedel <jroedel at suse.de> --- arch/alpha/kernel/pci-noop.c | 46 ++++---------------------------------------- 1 file changed, 4 insertions(+), 42 deletions(-) diff --git a/arch/alpha/kernel/pci-noop.c

On Fri, Oct 30, 2015 at 02:20:35PM +0100, Christian Borntraeger wrote: > +static void *dma_noop_alloc(struct device *dev, size_t size, > + dma_addr_t *dma_handle, gfp_t gfp, > + struct dma_attrs *attrs) > +{ > + void *ret; > + > + ret = (void *)__get_free_pages(gfp, get_order(size)); > + if (ret) { > + memset(ret, 0, size); There is no need to zero out the

Hello, I was looking at sys::getDefaultTargetTriple() (file: lib/Support/Unix/Host.inc ) and there is something unclear to me. std::string sys::getDefaultTargetTriple() { StringRef TargetTripleString(LLVM_DEFAULT_TARGET_TRIPLE); std::pair<StringRef, StringRef> ArchSplit = TargetTripleString.split('-'); // Normalize the arch, since the target triple may not actually