Nick Piggin wrote:
On Tue, Apr 17, 2007 at 02:25:39PM +1000, Peter Williams wrote:
Nick Piggin wrote:
On Mon, Apr 16, 2007 at 04:10:59PM -0700, Michael K. Edwards wrote:
On 4/16/07, Peter Williams [EMAIL PROTECTED] wrote:
Note that I talk of run queues
not CPUs as I think a shift to multiple
On Tue, Apr 17, 2007 at 02:17:22PM +1000, Peter Williams wrote:
I myself was thinking of this as the chance for a much needed
simplification of the scheduling code and if this can be done with the
result being reasonable it then gives us the basis on which to propose
improvements based on
On Tue, Apr 17, 2007 at 07:53:55AM +0200, Willy Tarreau wrote:
Hi Nick,
On Tue, Apr 17, 2007 at 06:29:54AM +0200, Nick Piggin wrote:
(...)
And my scheduler for example cuts down the amount of policy code and
code size significantly. I haven't looked at Con's ones for a while,
but I
On Tue, Apr 17, 2007 at 04:03:41PM +1000, Peter Williams wrote:
There's a lot of ugly code in the load balancer that is only there to
overcome the side effects of SMT and dual core. A lot of it was put
there by Intel employees trying to make load balancing more friendly to
their systems.
On Mon, Apr 16, 2007 at 11:09:55PM -0700, William Lee Irwin III wrote:
On Tue, Apr 17, 2007 at 02:17:22PM +1000, Peter Williams wrote:
I myself was thinking of this as the chance for a much needed
simplification of the scheduling code and if this can be done with the
result being
* Gene Heskett [EMAIL PROTECTED] wrote:
This one (v2-rc2) is not a keeper I'm sorry to say, Ingo. v2-rc0 was
much better. Watching amanda run with htop, kmails composer is being
subjected to 5 to 10 second pauses, and htop says that gzip -best
isn't getting more that 15% of the cpu, and
On Tue, Apr 17, 2007 at 04:03:41PM +1000, Peter Williams wrote:
Nick Piggin wrote:
But you add extra code for that on top of what we have, and are also
prevented from making per-cpu assumptions.
And you can get N CPUs per runqueue behaviour by having them in a domain
with no restrictions
Nick Piggin wrote:
On Tue, Apr 17, 2007 at 02:17:22PM +1000, Peter Williams wrote:
Nick Piggin wrote:
On Tue, Apr 17, 2007 at 04:29:01AM +0200, Mike Galbraith wrote:
On Tue, 2007-04-17 at 10:06 +1000, Peter Williams wrote:
Mike Galbraith wrote:
Demystify what? The casual observer need
On Mon, Apr 16, 2007 at 11:09:55PM -0700, William Lee Irwin III wrote:
All things are not equal; they all have different properties. I like
On Tue, Apr 17, 2007 at 08:15:03AM +0200, Nick Piggin wrote:
Exactly. So we have to explore those properties and evaluate performance
(in all meanings of
Nick Piggin wrote:
Well I know people have had woes with the scheduler for ever (I guess that
isn't going to change :P). I think people generally lost a bit of interest
in trying to improve the situation because of the upstream problem.
Yes.
Peter
--
Peter Williams
* Willy Tarreau [EMAIL PROTECTED] wrote:
Have you tried previous version with the fair-fork patch ? It might be
possible that your workload is sensible to the fork()'s child getting
much CPU upon startup.
the fair-fork patch is now included in -v2, but that was already in
-v2-rc0 too that
On Mon, April 16, 2007 23:57, Alan Cox wrote:
That is a fairly significant and sudden change to the existing
kernel/user interface.
Well, this is not meant for 2.6.21. I hope it is possible to change it
in
early 2.6.22; otherwise if we can't fix mistakes from the past we are
pretty
On Tue, Apr 17, 2007 at 04:23:37PM +1000, Peter Williams wrote:
Nick Piggin wrote:
And my scheduler for example cuts down the amount of policy code and
code size significantly.
Yours is one of the smaller patches mainly because you perpetuate (or
you did in the last one I looked at) the
Ingo Molnar wrote:
this is the second release of the CFS (Completely Fair Scheduler)
patchset, against v2.6.21-rc7:
http://redhat.com/~mingo/cfs-scheduler/sched-cfs-v2.patch
i'd like to thank everyone for the tremendous amount of feedback and
testing the v1 patch got - i could hardly keep
* Peter Williams [EMAIL PROTECTED] wrote:
Can I make a suggestion?
Would it be possible (from now on) to publish changes relevant to the
previous patch (eventually leading to a series of patches that
describes the evolution of the new scheduler) so that it's easier for
us
On Tue, 17 Apr 2007, Nick Piggin wrote:
All things are not equal; they all have different properties. I like
Exactly. So we have to explore those properties and evaluate performance
(in all meanings of the word). That's only logical.
I had a quick look at Ingo's code yesterday. Ingo is
On Mon, 2007-04-16 at 22:50 -0400, Joshua Wise wrote:
On Mon, 16 Apr 2007, Shaohua Li wrote:
On Sat, 2007-04-14 at 01:45 +0200, Mattia Dongili wrote:
...
please check if the patch at
http://marc.info/?l=linux-acpim=117523651630038w=2 fixed the issue
I have the same system as Mattia,
In net poll mode, the current checksum function doesn't consider the
kind of packet which is padded to reach a specific minimum length. I
believe that's the problem causing my test case failed. The following
patch fixed this issue.
Signed-off-by: Aubrey.Li [EMAIL PROTECTED]
---
On 15/04/07, Jesper Juhl [EMAIL PROTECTED] wrote:
On 14/04/07, David R. Litwin [EMAIL PROTECTED] wrote:
Before I go on, let me appologise. I don't really know what I hope to
accomplish, beyond trying to garner thoughts (and support?) for the
topic.
Essentially: I want to use Linux and ZFS.
Hi Pierre/philip,
This is regarding the MMCv4 support that came in as part of the MMC
core of 2.6.20 linux kernel version.
The high speed MMC cards can support 4-bit/8-bit transfers. The 8-bit
support seems to be missing from the MMCv4 support implemented by
Philip Langdale .
To support 8-bit
2007/4/17, Chuck Ebbert [EMAIL PROTECTED]:
Jan Engelhardt wrote:
On Apr 15 2007 12:53, Henrique de Moraes Holschuh wrote:
On Sat, 14 Apr 2007, Pavel Machek wrote:
How common are notebooks that cut power to disks during reboot?
Assuming it also does this when running Windows, I'd report it as
On Mon, Apr 16, 2007 at 11:26:21PM -0700, William Lee Irwin III wrote:
On Mon, Apr 16, 2007 at 11:09:55PM -0700, William Lee Irwin III wrote:
All things are not equal; they all have different properties. I like
On Tue, Apr 17, 2007 at 08:15:03AM +0200, Nick Piggin wrote:
Exactly. So we
* Ingo Molnar [EMAIL PROTECTED] wrote:
ok - fortunately the delta between -v2-rc0 and -v2-final is pretty
small. One difference is the child-runs-first fix. To restore the
parent-runs-first logic, do this:
echo 0 /proc/sys/kernel/sched_child_runs_first
does this make any
On 4/16/07, David Brownell [EMAIL PROTECTED] wrote:
No, all of those need to be done. (Plus maybe a few more things,
I wasn't trying to be exhaustive.) That last point is what makes
the other ones take effect ... without it, the top level IRQ will
never get dispatched to the GPIO-specific IRQ.
Brian D. McGrew a écrit :
Good evening gents!
I need some help in allocating memory and understanding how the system
allocates memory with physical versus virtual page tables. Please
consider the following snippet of code. Please, no wisecracks about bad
code; it was written in 30 seconds in
On Mon, Apr 16, 2007 at 11:50:03PM -0700, Davide Libenzi wrote:
I had a quick look at Ingo's code yesterday. Ingo is always smart to
prepare a main dish (feature) with a nice sider (code cleanup) to Linus ;)
And even this code does that pretty nicely. The deadline designs looks
good,
On Tue, 17 Apr 2007 12:53:10 +1000,
Rusty Russell [EMAIL PROTECTED] wrote:
On Mon, 2007-04-16 at 15:53 -0400, Alan Stern wrote:
The fundamental rule is that whenever you hand out a pointer to a routine
living in a module, the receiver has to increment the module's refcount.
But the
Make it possible for applications to have the kernel free memory
lazily. This reduces a repeated free/malloc cycle from freeing
pages and allocating them, to just marking them freeable. If the
application wants to reuse them before the kernel needs the memory,
not even a page fault will happen.
On Tue, 17 Apr 2007 01:51:08 -0400
Gene Heskett [EMAIL PROTECTED] wrote:
FWIW, I've been using the CFQ I/O scheduler for quite a while, is it time I
gave the AS or Deadline versions another check? They are all built in but I
don't know how to change the default on the fly, or even if it can
On Tue, 17 Apr 2007, Nick Piggin wrote:
To be clear, I'm not saying O(logN) itself is a big problem. Type
plot [10:100] x with lines, log(x) with lines, 1 with lines
Haha, Nick, I know how a log() looks like :)
The Time Ring I posted as example (that nothing is other than a
ring-based
William Lee Irwin III wrote:
On Mon, Apr 16, 2007 at 11:50:03PM -0700, Davide Libenzi wrote:
I had a quick look at Ingo's code yesterday. Ingo is always smart to
prepare a main dish (feature) with a nice sider (code cleanup) to Linus ;)
And even this code does that pretty nicely. The deadline
The latest version of the per device dirty throttling.
Dropped all the congestion_wait() churn, will contemplate a rename patch.
Reworked the BDI statistics to use percpu_counter.
against 2.6.21-rc6-mm1; the first patch is for easy application.
Andrew can of course just drop the patch it
On Tue, Apr 17, 2007 at 12:09:49AM -0700, William Lee Irwin III wrote:
The trouble with thorough testing right now is that no one agrees on
what the tests should be and a number of the testcases are not in great
shape. An agreed-upon set of testcases for basic correctness should be
devised
Count per BDI dirty pages.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
fs/buffer.c |1 +
include/linux/backing-dev.h |1 +
mm/page-writeback.c |2 ++
mm/truncate.c |1 +
4 files changed, 5 insertions(+)
Index:
Scale writeback cache per backing device, proportional to its writeout speed.
By decoupling the BDI dirty thresholds a number of problems we currently have
will go away, namely:
- mutual interference starvation (for any number of BDIs);
- deadlocks with stacked BDIs (loop, FUSE and local NFS
Provide scalable per backing_dev_info statistics counters.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/linux/backing-dev.h | 50 ++--
mm/backing-dev.c| 26 ++
2 files changed, 74 insertions(+), 2
On Mon, 16 Apr 2007 15:12:47 -0700,
Greg KH [EMAIL PROTECTED] wrote:
Ah, just found this original thread, now Cornelia's patches make more
sense...
I would have included a pointer, but couldn't access marc yesterday
evening, sorry...
On Fri, Apr 13, 2007 at 11:24:58AM -0400, Alan Stern
Expose the per BDI stats in /sys/block/dev/queue/*
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
block/ll_rw_blk.c | 32
1 file changed, 32 insertions(+)
Index: linux-2.6-mm/block/ll_rw_blk.c
With the current logic the percpu_counter's accuracy delta is quadric
wrt the number of cpus in the system, reduce this to O(n ln n).
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/linux/percpu_counter.h |7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
Index:
provide BDI constructor/destructor hooks
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
block/ll_rw_blk.c |2 ++
drivers/block/rd.c |6 ++
drivers/char/mem.c |2 ++
drivers/mtd/mtdcore.c |5 +
fs/char_dev.c
Expose the per BDI stats in /sys/block/dev/queue/*
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
block/ll_rw_blk.c | 49 +
mm/page-writeback.c |2 +-
2 files changed, 50 insertions(+), 1 deletion(-)
Index: linux-2.6/block/ll_rw_blk.c
For ease of application..
---
block/ll_rw_blk.c | 29 -
fs/buffer.c |1 -
include/linux/backing-dev.h |2 --
mm/page-writeback.c | 13 ++---
mm/truncate.c |1 -
5 files changed, 2 insertions(+),
Its redundant, clear_bdi_congested() already wakes the waiters.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
fs/nfs/write.c |4 +---
include/linux/backing-dev.h |1 -
mm/backing-dev.c| 13 -
3 files changed, 1 insertion(+), 17 deletions(-)
Count per BDI writeback pages.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/linux/backing-dev.h |1 +
mm/page-writeback.c | 12 ++--
2 files changed, 11 insertions(+), 2 deletions(-)
Index: linux-2.6/mm/page-writeback.c
Add percpu_counter_mod64() to allow large modifications.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/linux/percpu_counter.h |9 +
lib/percpu_counter.c | 28
2 files changed, 37 insertions(+)
Index:
On Tue, 17 Apr 2007, William Lee Irwin III wrote:
On Mon, Apr 16, 2007 at 11:50:03PM -0700, Davide Libenzi wrote:
I would suggest to thoroughly test all your alternatives before deciding.
Some code and design may look very good and small at the beginning, but
when you start patching it
On 4/17/07, Christoph Lameter [EMAIL PROTECTED] wrote:
The flag SLAB_MUST_HWCACHE_ALIGN is
1. Never checked by SLAB at all.
2. A duplicate of SLAB_HWCACHE_ALIGN for SLUB
3. Fulfills the role of SLAB_HWCACHE_ALIGN for SLOB.
The only remaining use is in sparc64 and ppc64 and their use there
On Tue, 17 Apr 2007, Ingo Molnar wrote:
* Ingo Molnar [EMAIL PROTECTED] wrote:
ok - fortunately the delta between -v2-rc0 and -v2-final is pretty
small. One difference is the child-runs-first fix. To restore the
parent-runs-first logic, do this:
echo 0
On Tue, Apr 17, 2007 at 12:27:28AM -0700, Davide Libenzi wrote:
On Tue, 17 Apr 2007, William Lee Irwin III wrote:
On Mon, Apr 16, 2007 at 11:50:03PM -0700, Davide Libenzi wrote:
I would suggest to thoroughly test all your alternatives before deciding.
Some code and design may look very
* William Lee Irwin III [EMAIL PROTECTED] wrote:
On Mon, Apr 16, 2007 at 11:50:03PM -0700, Davide Libenzi wrote:
I had a quick look at Ingo's code yesterday. Ingo is always smart to
prepare a main dish (feature) with a nice sider (code cleanup) to
Linus ;) And even this code does that
On Mon, 16 Apr 2007 15:38:52 -0400 (EDT),
Alan Stern [EMAIL PROTECTED] wrote:
On Mon, 16 Apr 2007, Dmitry Torokhov wrote:
Unfortunately all this wait for refcount in module's exit schemas
lead to the following deadlock:
rmmod my_module
Hi.
On 4/17/07, Chuck Ebbert [EMAIL PROTECTED] wrote:
snip
(2) Linux (alone) gives a very muted pop on shutdown. This could
be from bad interaction with the shutdown command, or some
other reason (drive not given enough time to shut down?)
The noise is not very loud, maybe the head
* Davide Libenzi [EMAIL PROTECTED] wrote:
ok, i've got something better to test: i separated the delta out
into a more finegrained stack of 3 patches. You can pick them up
from:
http://redhat.com/~mingo/cfs-scheduler/older/sched-cfs-v2-rc0.patch
On Tue, Apr 17, 2007 at 09:33:08AM +0200, Ingo Molnar wrote:
* William Lee Irwin III [EMAIL PROTECTED] wrote:
On Mon, Apr 16, 2007 at 11:50:03PM -0700, Davide Libenzi wrote:
I had a quick look at Ingo's code yesterday. Ingo is always smart to
prepare a main dish (feature) with a nice
On Mon, 16 Apr 2007 17:02:46 -0400 (EDT),
Alan Stern [EMAIL PROTECTED] wrote:
No, only the core module has to stay. For example, every time you
register an input device you pin input.ko as it is the module that
provides -release() method for input devices. You can freely unload
psmouse,
Nick Piggin wrote:
On Tue, Apr 17, 2007 at 04:23:37PM +1000, Peter Williams wrote:
Nick Piggin wrote:
And my scheduler for example cuts down the amount of policy code and
code size significantly.
Yours is one of the smaller patches mainly because you perpetuate (or
you did in the last one I
Ingo Molnar wrote:
this is the second release of the CFS (Completely Fair Scheduler)
patchset, against v2.6.21-rc7:
http://redhat.com/~mingo/cfs-scheduler/sched-cfs-v2.patch
i'd like to thank everyone for the tremendous amount of feedback and
testing the v1 patch got - i could hardly
On Tue, Apr 17, 2007 at 05:48:55PM +1000, Peter Williams wrote:
Nick Piggin wrote:
Other hints that it was a bad idea was the need to transfer time slices
between children and parents during fork() and exit().
I don't see how that has anything to do with dual arrays.
It's totally to do
Ingo Molnar wrote:
[announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS]
i'm pleased to announce the first release of the Modular Scheduler Core
and Completely Fair Scheduler [CFS] patchset:
http://redhat.com/~mingo/cfs-scheduler/sched-modular+cfs.patch
This
* Nick Piggin [EMAIL PROTECTED] wrote:
Anyone who thinks that there exists only two kinds of code: 100%
correct and 100% incorrect with no shades of grey inbetween is in
reality a sort of an extremist: whom, depending on mood and
affection, we could call either a 'coding purist' or a
William Lee Irwin III wrote:
On Tue, Apr 17, 2007 at 04:34:36PM +1000, Peter Williams wrote:
This doesn't make any sense to me.
For a start, exact simultaneous operation would be impossible to achieve
except with highly specialized architecture such as the long departed
transputer. And
QLA1280: call pci_set_dma_mask with DMA_64BIT_MASK instead of ~ 0ULL
Signed-off-by: Matthias Kaehlcke [EMAIL PROTECTED]
---
diff --git a/drivers/scsi/qla1280.c b/drivers/scsi/qla1280.c
index 6777e8a..54d8bdf 100644
--- a/drivers/scsi/qla1280.c
+++ b/drivers/scsi/qla1280.c
@@ -4293,7 +4293,7 @@
On Tue, 17 Apr 2007, Ingo Molnar wrote:
ok - fortunately the delta between -v2-rc0 and -v2-final is pretty
small. One difference is the child-runs-first fix. To restore the
parent-runs-first logic, do this:
echo 0 /proc/sys/kernel/sched_child_runs_first
Sorry, I did not follow
Hi,
On Wed, 04 Apr 2007 07:03:55 +0200, Eric Dumazet wrote:
find net | xargs grep -n SIOCINQ
I suspect you will find unix_ioctl() in net/unix/af_unix.c ?
BTW, my patch only worked for pipes, not fifos. Ie pipe(), not
open(/some/fifo.p, ...)
Thanks for your patch. There is a question however;
Neil Brown wrote:
On Monday April 16, [EMAIL PROTECTED] wrote:
cfq_dispatch_insert() was called with rq == 0. This one is getting really
annoying... and md is involved again (RAID0 this time.)
Yeah... weird.
RAID0 is so light-weight and so different from RAID1 or RAID5 that I
feel fairly safe
* William Lee Irwin III [EMAIL PROTECTED] wrote:
On Tue, Apr 17, 2007 at 04:46:57PM +1000, Peter Williams wrote:
Have you considered using rq-raw_weighted_load instead of
rq-nr_running in calculating fair_clock? This would take the nice
value (or RT priority) of the other tasks into
Hi!
+ /* Calculate the empty level at the present temperature. */
+ scale[4] = di-raw[DS2760_ACTIVE_EMPTY + 4];
+ for (i = 3; i = 0; i--)
+ scale[i] = scale[i + 1] + di-raw[DS2760_ACTIVE_EMPTY + i];
+
+ di-empty_mAh = battery_interpolate(scale, di-temp_C /
Have you tried other combinations?
s2ram -m -p -f
s2ram -s -p -f
Yes, I tried these slightly different combinations:
s2ram -f -a3 -s: Works! The screen becomes green but is restored quickly. It
prints the following messages:
Allocated buffer at 0x11000 (base is 0x0)
ES: 0x1100 EBX: 0x
FUSE is nice for trying out new and interresting ideas in userspace -
it has its uses.
Yes, but it is not really for the end-user. To paraphrase another, it is
mostly academic.
Oh? I thought those ~10,000 downloads of SSHFS and ~200,000 downloads
of NTFS-3G were end users.(*)
Maybe I
On Tue, Apr 17, 2007 at 01:03:46AM -0700, Davide Libenzi wrote:
On Tue, 17 Apr 2007, Ingo Molnar wrote:
ok - fortunately the delta between -v2-rc0 and -v2-final is pretty
small. One difference is the child-runs-first fix. To restore the
parent-runs-first logic, do this:
echo 0
* Davide Libenzi [EMAIL PROTECTED] wrote:
ok - fortunately the delta between -v2-rc0 and -v2-final is pretty
small. One difference is the child-runs-first fix. To restore the
parent-runs-first logic, do this:
echo 0 /proc/sys/kernel/sched_child_runs_first
Sorry, I did not
On Mon, Apr 16, 2007 at 11:26:21PM -0700, William Lee Irwin III wrote:
Any chance you'd be willing to put down a few thoughts on what sorts
of standards you'd like to set for both correctness (i.e. the bare
minimum a scheduler implementation must do to be considered valid
beyond not oopsing)
On Mon, Apr 16, 2007 at 04:10:59PM -0700, Michael K. Edwards wrote:
This observation of Peter's is the best thing to come out of this
whole foofaraw. Looking at what's happening in CPU-land, I think it's
going to be necessary, within a couple of years, to replace the whole
idea of CPU
* Nick Piggin [EMAIL PROTECTED] wrote:
Actually I think this is something that makes sense to add, even if
just for debugging, but maybe also for production, depending on how
much it impacts things. Child runs first is an heuristic optimisation
that exploits a VM detail (however
William Lee Irwin III wrote:
Ingo Molnar wrote:
this is the second release of the CFS (Completely Fair Scheduler)
patchset, against v2.6.21-rc7:
http://redhat.com/~mingo/cfs-scheduler/sched-cfs-v2.patch
i'd like to thank everyone for the tremendous amount of feedback and
testing the v1
On Tue, Apr 17, 2007 at 10:26:31AM +0200, Ingo Molnar wrote:
* Nick Piggin [EMAIL PROTECTED] wrote:
Actually I think this is something that makes sense to add, even if
just for debugging, but maybe also for production, depending on how
much it impacts things. Child runs first is an
On 17/04/07, Miklos Szeredi [EMAIL PROTECTED] wrote:
Yes, but it is not really for the end-user. To paraphrase another, it is
mostly academic.
Oh? I thought those ~10,000 downloads of SSHFS and ~200,000 downloads
of NTFS-3G were end users.(*)
Maybe I was wrong though. Thanks for the
* Peter Williams [EMAIL PROTECTED] wrote:
And my scheduler for example cuts down the amount of policy code and
code size significantly.
Yours is one of the smaller patches mainly because you perpetuate (or
you did in the last one I looked at) the (horrible to my eyes) dual
array
Hi Mark,
On Sun, 15 Apr 2007 11:03:20 -0400, Mark M. Hoffman wrote:
Hi Jean, et al:
* Jean Delvare [EMAIL PROTECTED] [2007-04-10 15:02:27 +0200]:
I am resigning from my role as hardware monitoring subsystem
(drivers/hwmon) maintainer. This is too much work for me, I do not have
the
* Ingo Molnar [EMAIL PROTECTED] wrote:
* William Lee Irwin III [EMAIL PROTECTED] wrote:
On Tue, Apr 17, 2007 at 04:46:57PM +1000, Peter Williams wrote:
Have you considered using rq-raw_weighted_load instead of
rq-nr_running in calculating fair_clock? This would take the
nice
If the kernel OOPS-ed or BUG-ed then it probably should
considered as tainted. Use die_counter introduced by many
architectures to determine whether or not the kernel died.
This saves a lot of time explaining oddities in the
calltrace seen via SysRq-P.
Signed-off-by: Pavel Emelianov [EMAIL
* Nick Piggin [EMAIL PROTECTED] wrote:
list_add_tail(p-run_list, current-run_list);
[...]
shouldnt the list_add_tail() be list_add(), so that task pickup sees
the child first? [...]
[...]
I think that it works because the list we're adding to is not the
normal
* S.Çağlar Onur [EMAIL PROTECTED] wrote:
17 Nis 2007 Sal tarihinde, Ingo Molnar şunları yazmıştı:
- fixed child-runs first. A /proc/sys/kernel/sched_child_runs_first
flag can be used to turn it on/off. (This might fix the Kaffeine bug
reported by S.Çağlar Onur )
Sorry for
Serge E. Hallyn [EMAIL PROTECTED] writes:
Why are directory permissions not sufficient to allow/deny non-priveleged
mounts?
I don't understand that contention yet.
The same scenarios laid out previously in this thread. I.e.
1. user hallyn does mount --bind / /home/hallyn/root
2. (...)
The return value of lookup_one_len() is used without testing for error return.
This results in the following oops when SELinux is enabled and enforced. The
reason for the Oops is as follows.
The shell's (bash) SELinux domain is not allowed search permission in
sysfs
filesystem (type
* William Lee Irwin III [EMAIL PROTECTED] wrote:
The additive nice_offset breaks nice levels. A multiplicative priority
weighting of a different, nonnegative metric of cpu utilization from
what's now used is required for nice levels to work. I've been trying
to point this out politely by
* William Lee Irwin III [EMAIL PROTECTED] wrote:
[...] Also rest assured that the tone of the critique is not hostile,
and wasn't meant to sound that way.
ok :) (And i guess i was too touchy - sorry about coming out swinging.)
Also, given the general comments it appears clear that some
On Tue, 2007-04-17 at 10:17 +0200, Marcus Better wrote:
Have you tried other combinations?
s2ram -m -p -f
s2ram -s -p -f
Yes, I tried these slightly different combinations:
s2ram -f -a3 -s: Works! The screen becomes green but is restored quickly. It
prints the following messages:
On Tue, Apr 17, 2007 at 08:56:27AM +0100, Andy Whitcroft wrote:
as usual, any sort of feedback, bugreports, fixes and suggestions are
more than welcome,
Pushed this through the test.kernel.org and nothing new blew up.
Notably the kernbench figures are within expectations even on the
* Peter Williams [EMAIL PROTECTED] wrote:
There's a lot of ugly code in the load balancer that is only there to
overcome the side effects of SMT and dual core. A lot of it was put
there by Intel employees trying to make load balancing more friendly
to their systems. What I'm suggesting
* Nick Piggin [EMAIL PROTECTED] wrote:
Maybe the progress is that more key people are becoming open to
the idea of changing the scheduler.
Could be. All was quiet for quite a while, but when RSDL showed up,
it aroused enough interest to show that scheduling woes is on folks
* Peter Williams [EMAIL PROTECTED] wrote:
Have you considered using rq-raw_weighted_load instead of
rq-nr_running in calculating fair_clock? This would take the nice
value (or RT priority) of the other tasks into account when
determining what's fair.
Peter
PS You'd have to change
* William Lee Irwin III [EMAIL PROTECTED] wrote:
Also, given the general comments it appears clear that some
statistical metric of deviation from the intended behavior furthermore
qualified by timescale is necessary, so this appears to be headed
toward a sort of performance metric as
Remove duplicate define of OHCI_QUIRK_ZFMICRO from ftdi-elan.c, its already
defined in drivers/ush/host/ohci.c
Signed-off-by: S.Çağlar Onur [EMAIL PROTECTED]
diff --git a/drivers/usb/misc/ftdi-elan.c b/drivers/usb/misc/ftdi-elan.c
index bc3327e..a283816 100644
--- a/drivers/usb/misc/ftdi-elan.c
At Tue, 17 Apr 2007 10:01:47 +0530,
[EMAIL PROTECTED] wrote:
From: Abhijit Bhopatkar [EMAIL PROTECTED]
First generation MacBooks were getting ignored by sigmatel drivers
and wrongly being identified as MACMINI. This patch makes them
identify as MACBOOK.
Signed-off-by: Abhijit Bhopatkar
* Nick Piggin [EMAIL PROTECTED] wrote:
2.6.21-rc7-cfs-v2
534.80user 30.92system 2:23.64elapsed 393%CPU
534.75user 31.01system 2:23.70elapsed 393%CPU
534.66user 31.07system 2:23.76elapsed 393%CPU
534.56user 30.91system 2:23.76elapsed 393%CPU
534.66user 31.07system 2:23.67elapsed 393%CPU
* William Lee Irwin III [EMAIL PROTECTED] wrote:
On Tue, Apr 17, 2007 at 11:24:22AM +0200, Ingo Molnar wrote:
until now the main approach for nice levels in Linux was always:
implement your main scheduling logic for nice 0 and then look for
some low-overhead method that can be glued to
Hi Bjorn, Luca,
On Mon, 16 Apr 2007 23:14:11 +0200, Luca Tettamanti wrote:
Il Sun, Apr 15, 2007 at 06:57:02PM -0600, Bjorn Helgaas ha scritto:
In the case of k8temp, the driver claims PCI devices with a certain
vendor and device ID. PCI devices are mostly outside the scope of
ACPI.
At Mon, 16 Apr 2007 17:44:57 -0400,
Chuck Ebbert wrote:
Adrian Bunk wrote:
This email lists some known regressions in Linus' tree compared to 2.6.20.
Subject: snd_intel8x0: divide error:
References : http://lkml.org/lkml/2007/3/5/252
Submitter : Michal Piotrowski [EMAIL
On Mon, 16 Apr 2007, Andi Kleen wrote:
On Tue, Apr 17, 2007 at 12:28:31AM +0300, Mikko Tiihonen wrote:
I actually was more worried that someone might complain that the pci
scanning is copy paste code from end of the same file. I did try to use
the generic pci functions first but because they
1 - 100 of 877 matches
Mail list logo
