Displaying 5 results from an estimated 5 matches for "schedues".
Did you mean:
schedules
2003 Apr 02
1
Kernel lockup (kjournald?)
I am getting an odd situation when backing up a number of ext3 filesystems
and was wondering if it could be caused by journalling. Over the space of
a minute the load average will jump from 2 to over 40 and the system will
be unresponsive for anywhere from 8 to 25 minutes. I am going to be trying
a number of things, but was wondering if anyone could see the reason for
the high load given the
2010 Aug 11
1
[LLVMdev] Need advice on writing scheduling pass
Hello LLVM developers,
I have a few questions regarding the passes that are run after instruction
selection and before register allocation. I am writing a scheduling pass
(modulo scheduling). Before I ask my questions, I will first try to explain
the approach I am taking.
- Currently, I am running the passes in the following order.
(-debug-pass=Structure output)
Remove unreachable machine
2008 Feb 13
1
Re: Disk partitions and LVM limits - SUMMARY
Thank you all for the help.
I'm writing this summary message because of people requests. I haven't tried
all of this. I just collected it and organized it.
You've got a big storage. Now what?
The short answer is: "Just connect it. It should work."
I'll play safe by saying that the following applies to <10TB storage. Some
people reported file systems of 80TB.
2003 Apr 16
2
smbmount often doesn't go daemon
Hi,
Since i upgraded to Linux Redhat 9.0 / samba-2.2.7a-8.9.0 / kernel 2.4.20-9
i have the following problem:
# smbmount //amd/Films /mnt/disk -o username=jan,password=XXXXXX
#
In 50% of the times i do this command it mounts the share and goes into
daemon mode and ps -aux shows one process smbmount. All ok.
However in the other 50% the command just hangs. If i open a new window
it did do
2011 May 24
4
[LLVMdev] Need advice on writing scheduling pass
Hi (Jakob),
in reference to the prior message below, I have the following follow-up questions, as I also need a scheduling pass
prior to regalloc. I need to do this in order to set VLIW-flags, so that the RA is aware of several MI's
per cycle with a redefined LiveRange::overlap-function. On a multiple-issue cycle, a register that gets killed
can be reused by another MI - these live ranges do