We have logic to detect whether the system has migratable tasks, but we are not using it when deciding whether to push tasks away. So we add support for considering this new information. Signed-off-by: Gregory Haskins <ghaskins@novell.com> --- kernel/sched.c | 2 ++ kernel/sched_rt.c | 10 ++++++++-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/kernel/sched.c b/kernel/sched.c index 8a27f09..0eced8c 100644 --- a/kernel/sched.c +++ b/kernel/sched.c @@ -268,6...

The current wake-up code path tries to determine if it can optimize the wake-up to "this_cpu" by computing load calculations. The problem is that these calculations are only relevant to CFS tasks where load is king. For RT tasks, priority is king. So the load calculation is completely wasted bandwidth. Therefore, we create a new sched_class interface to help with pre-wakeup routing decisions and move the load calculation as a function of CFS task's class. Signed-off-by: Gregory Haskins <gh...

In the original patch series that Steven Rostedt and I worked on together, we both took different approaches to low-priority wakeup path. I utilized "pre-routing" (push the task away to a less important RQ before activating) approach, while Steve utilized a "post-routing" approach. The advantage of my approach is that you avoid the overhead of a wasted activate/deactivate cycle and peripherally related burdens. The advantage of Steve's method is that it neatly solves an issue preventing a "pull" op...

"this_rq" is normally used to denote the RQ on the current cpu (i.e. "cpu_rq(this_cpu)"). So clean up the usage of this_rq to be more consistent with the rest of the code. Signed-off-by: Gregory Haskins <ghaskins@novell.com> --- kernel/sched_rt.c | 46 +++++++++++++++++++++++----------------------- 1 files changed, 23 insertions(+), 23 deletions(-) diff --git a/kernel/sched_rt.c b/kernel/sched_rt.c index 9b06d7c..0348423 100644 --- a/kernel/sched_rt.c +++ b/kernel/sched_rt.c @@ -3...

Problem is repeatable on my computer. It dies in __module_get() on this line: BUG_ON(module_refcount(module) == 0); I think this is because commit 7b595756ec1f49e0049a9e01a1298d53a7faaa15, which states: "Note that with this change, userland holding a sysfs node does not prevent the backing module from being unloaded." Unfortunately, I don't know how this sysfs stuff is supposed to work, and therefore don't know how to fix the problem. -- Peter Osterlund - petero2@telia.com http:/...

Keeping the list in sync with the old IDE driver Signed-off-by: Alan Cox <alan@redhat.com> diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.24-rc1/drivers/ata/ata_piix.c linux-2.6.24-rc1/drivers/ata/ata_piix.c --- linux.vanilla-2.6.24-rc1/drivers/ata/ata_piix.c 2007-11-01 11:41:54.000000000 +0000 +++ linux-2.6.24-rc1/drivers/ata/ata_piix.c 2007-11-05 22:25:32.879377872 +0000 @@ -621,6 +621,7 @@ static const struct ich_laptop ich_laptop[] = { /* devid, subv...

Here are a some PCI patches against your 2.6.24-rc1 git tree. They are a bunch of quirk updates from David Miller, a new config item to help Jeff Garzik start to cleanup the isdn drivers and let him take those patches through his tree, and a few other minor bugfixes. All of these have been in the -mm tree for a while. Please pull from: master.kernel.org:/pub/scm/linux/kernel/git/gregkh/pci-2.6.git/ The full patches will be sent to the linux-pci mailing list, if anyone wants to see them. ...

I'll defer to David on this one, as he sent it to me. David? greg k-h -

Btw, I'd also like to take the opportunitity to ask people to always include the explanation of the commit when you give a commit ID. "git revert" does that for the commit it reverts, but the (bogus) commit ID that was apparently added by David (c129d962a) didn't get the explanation for it, so now it's totally impossible to match it up with anything at all.. So let me one more say: - don't just say .. was cured by commit xyz - but add the one-liner description of the commit,...

Side note: I pulled and pushed out, since I assume the *code* is correct, but please double-check the commit messages for things like this. gitk makes it really easy, since it will highlight valid commit ID's. It looks lik eyou may have re-ordered the commits or something? Linus -

Well, I suspect that David referred to a commit that he just sent by email. Which obviously will have a *different* commit ID once you commit it - so it probably made sense in his tree, but not once he exported it as an email instead of syncing with git natively. I also suspect that the whole series was re-ordered in email (or by you reading/applying them in a different order). Since now the revert of the "disable MSI" happens *before* the patch that looks like it will fix the issue. ...

Greg: So what's our status? Do you think it's worthwhile adding the "drop reference to parent kobject at remove time instead of release time" patch? Also, what's the story on the updates to the USB uevent routines? Do you want separate patches from Kay and me or should we combine them into a single patch? Alan Stern -

[...] The controller itself cannot be initialized anymore. The message "MMIO resource... unavailable" is because ohci1394's call to request_mem_region failed, i.e. when it tried to request the memory-mapping of controller registers. I have no idea how this could happen, therefore I Cc lkml. It's not a problem with the IEEE 1394 drivers. Besides the kernel update, did you change anything in the BIOS or even the hardware? Do you boot the old kernels with the same boot parameters as you did b...

Annotate sas_queuecommand with locking details, and clean up a few more sparse warnings about static/non-static declarations. Signed-off-by: Darrick J. Wong <djwong@us.ibm.com> --- drivers/scsi/libsas/sas_scsi_host.c | 6 +++++- include/scsi/libsas.h | 4 +--- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/drivers/scsi/libsas/sas_scsi_host.c b/drivers/scsi/libsas/sas_scsi_host.c index 0fa0296..c29ba47 100644 --- a/drivers/scsi/libsas/sas_scsi_host.c ...

ACK patches 1-2 -

Suggested by Geert Uytterhoeven - use const.h to get constants that are usable in both C and assembly. I can't include it directly since this code can't include kernel headers. const.h is also for numeric constants that can be typed by tacking a "UL" or similar on the end. The constants here have to be typed by casting them. So, the relevant parts of const.h are copied here and modified in order to allow the constants to be uncasted in assembly and casted in C. Signed-off-by: Jeff Dike <jdi...

These six patches are cleanups and can wait until 2.6.25. Jeff -- Work email - jdike at linux dot intel dot com -

From: WANG Cong <xiyou.wangcong@gmail.com> This patch also does some improvements for uml code. Improvements include dropping unnecessary cast, killing some unnecessary code and still some constifying for pointers etc.. Signed-off-by: WANG Cong <xiyou.wangcong@gmail.com> Signed-off-by: Jeff Dike <jdike@linux.intel.com> --- arch/um/drivers/ubd_kern.c | 6 +++--- arch/um/include/kern_util.h | 2 +- arch/um/kernel/mem.c | 2 +- ...

Notice "hung" not "hangs". This happened so far only once - when low batter= y=20 condition triggered suspend to disk. I was not able to reproduce it after=20 this running on AC. Just in case it rings the bell for someone. This is not suspend regression= =20 reported earlier by Jens - I do not even have SATA nor is using libata=20 drivers. =2Dandrey

Mirror and linear data stripping algorithms for DST. Signed-off-by: Evgeniy Polyakov <johnpol@2ka.mipt.ru> diff --git a/drivers/block/dst/alg_linear.c b/drivers/block/dst/alg_linear.c new file mode 100644 index 0000000..cb77b57 --- /dev/null +++ b/drivers/block/dst/alg_linear.c @@ -0,0 +1,104 @@ +/* + * 2007+ Copyright (c) Evgeniy Polyakov <johnpol@2ka.mipt.ru> + * All rights reserved. + * + * This program is free software; you can redistribute it and/or modify + * it under the ...

This file contains all bits needed for async non-blocking network processing of the block requests directed to DST. Signed-off-by: Evgeniy Polyakov <johnpol@2ka.mipt.ru> diff --git a/drivers/block/dst/kst.c b/drivers/block/dst/kst.c new file mode 100644 index 0000000..ba5e5ef --- /dev/null +++ b/drivers/block/dst/kst.c @@ -0,0 +1,1475 @@ +/* + * 2007+ Copyright (c) Evgeniy Polyakov <johnpol@2ka.mipt.ru> + * All rights reserved. + * + * This program is free software; you can redi...

Hi. I'm pleased to announce 7'th and the final release of the distributed storage subsystem (DST). It allows to form a storage on top of local and remote nodes and combine them in linear or mirroring setup, which in turn can be exported to remote nodes. Short changelog: * added strong checksum support (Castagnoli crc) * extended autoconfiguration (added ability to request if remote side supports strong checksum and turn it on if needed) * documentation addon - sysfs files * added clean/dirty ...

For the last release, I stated that I thought the 2.6.22.12 release would be the last one in the 2.6.22.y series. Since then, I've received a number of other patches that would be nice to have in the .22.y tree. So, for a while, I'll keep the 2.6.22.y tree open, doing new releases every once in a while as they accumulate. I do this, for no other than the selfish reason that I use it every day on my openSuSE 10.3 boxes as that is the kernel base that release is on :) If anyone has any objections...

diff --git a/Makefile b/Makefile index 8874c9b..b55f9bf 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ VERSION = 2 PATCHLEVEL = 6 SUBLEVEL = 22 -EXTRAVERSION = .11 +EXTRAVERSION = .12 NAME = Holy Dancing Manatees, Batman! # *DOCUMENTATION* diff --git a/arch/i386/kernel/io_apic.c b/arch/i386/kernel/io_apic.c index 7f8b7af..97ba305 100644 --- a/arch/i386/kernel/io_apic.c +++ b/arch/i386/kernel/io_apic.c @@ -1275,12 +1275,15 @@ static struct irq_chip ioapic_chip; static void ioa...

For quite some time I'm seeing occasional lockups spread over 50 different machines I'm maintaining. Symptom: a page allocation failure with order:1, GFP_ATOMIC, while there is plenty of memory, as it seems (lots of free pages, almost no swap used) followed by a lockup (everything dead). I've collected all (12) crash cases which occurred the last 10 weeks on 50 machines total (i.e. 1 crash every 41 weeks on average). The kernel messages are summarized to show the interesting part (IMO) they have in c...