On Wed, 18 Apr 2007, Davide Libenzi wrote:
I know, we agree there. But that did not fit my Pirates of the Caribbean
quote :)
Ahh, I'm clearly not cultured enough, I didn't catch that reference.
Linus yes, I've seen the movie, but it
apparently left more of a mark
On Wed, 2007-04-18 at 11:20 -0400, Alan Stern wrote:
On Wed, 18 Apr 2007, Rusty Russell wrote:
Hi Alan,
Your assertion is correct. I haven't studied the driver core, so I
might be off-base here, but you'll note that if the module references
the core kmalloc'ed object rather than
Chuck Ebbert wrote:
Denis Vlasenko wrote:
* From make menuconfig questions it looks like SATA/PATA
rewrite (in the form of libata) is almost finished. Hehe,
untangling IDE mess was quite a feat, and Jeff did it. Kudos.
ADMA mode on nvidia chipsets still seems broken despite massive
Chris Friesen wrote:
Mark Glines wrote:
One minor question: is it even possible to be completely fair on SMP?
For instance, if you have a 2-way SMP box running 3 applications, one of
which has 2 threads, will the threaded app have an advantage here? (The
current system seems to try to keep
liangbowen wrote:
Hi
I compiled the following code with gcc under FC2 :
#include asm/semaphore.h
main()
{
struct semaphore sum;
}
It doesn't compile, saying storage size of `sem'
isn't known.
and I looked inside asm/semaphore.h, I saw:
#ifndef I386_SEMAPHORE_H
#define I386_SEMAPHORE_H
On 4/18/07, David Howells [EMAIL PROTECTED] wrote:
Aubrey Li [EMAIL PROTECTED] wrote:
Here, in the attachment I wrote a small test app. Please correct if
there is anything wrong, and feel free to improve it.
Okay... I have that working... probably. I don't know what output it's
supposed to
On Wed, 2007-04-18 at 19:00 -0400, Joshua Wise wrote:
On Tue, 17 Apr 2007, Shaohua Li wrote:
Looks there is init order issue of sysfs files. The new refreshed patch
should fix your bug.
Yes, that did fix the hang on resume from STR -- that now works fine.
However:
[EMAIL
I've seen a lot of systems (including brand new Xeon-based servers from
IBM and HP) that output messages on boot like:
PCI: BIOS Bug: MCFG area at f000 is not E820-reserved
PCI: Not using MMCONFIG.
As I understand it, this is sort of a sanity check mechanism to make
sure the MCFG address
John == John Stoffel [EMAIL PROTECTED] writes:
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
Alan me
Hi.
On Thu, 2007-04-19 at 00:22 +0200, Christian Hesse wrote:
On Thursday 19 April 2007, Ingo Molnar wrote:
* Christian Hesse [EMAIL PROTECTED] wrote:
although probably your suspend2 problem is still not fixed, it's
worth a try nevertheless. Which suspend2 patch did you apply, and
Hi all,
Anyone has idea of this: Why it is displayed on boot? How to fix this? Or at
least not to display this message?
Using 2.6.9-42.ELsmp.
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller :00:1f.1
PCI: Unable to handle 64-bit address space for
PCI: Unable to
Hi.
On Wed, 2007-04-18 at 18:56 -0400, Bob Picco wrote:
Ingo Molnar wrote:[Wed Apr 18 2007, 06:02:28PM EDT]
* Christian Hesse [EMAIL PROTECTED] wrote:
although probably your suspend2 problem is still not fixed, it's
worth a try nevertheless. Which suspend2 patch did you
John == John Stoffel [EMAIL PROTECTED] writes:
John == John Stoffel [EMAIL PROTECTED] writes:
Ok, so do I need to do anything special with the next -mm release and
the next version?
Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).
Alan Try drivers/ide/pci/hpt366
On Wed, Apr 18, 2007 at 10:11:46AM -0400, Trond Myklebust wrote:
Do you have a copy of wireshark or ethereal on hand? If so, could you
take a look at whether or not any NFS traffic is going between the
client and server once the hang happens?
I used the following command
tcpdump -w
Hi.
On Thu, 2007-04-19 at 00:02 +0200, Ingo Molnar wrote:
* Christian Hesse [EMAIL PROTECTED] wrote:
although probably your suspend2 problem is still not fixed, it's
worth a try nevertheless. Which suspend2 patch did you apply, and
was it against -rc6 or -rc7?
You are right
On Thursday 19 April 2007 09:48, Con Kolivas wrote:
While the Staircase Deadline scheduler has not been completely killed off
and is still in -mm I would like to fix some outstanding issues that I've
found since it still serves for comparison with all the upcoming
schedulers.
While still in
Christoph Lameter wrote:
On Wed, 21 Mar 2007, Ethan Solomita wrote:
Christoph Lameter wrote:
On Thu, 1 Feb 2007, Ethan Solomita wrote:
Hi Christoph -- has anything come of resolving the NFS / OOM concerns
that
Andrew Morton expressed concerning the patch? I'd be happy to
On Thursday 19 April 2007 10:41, Con Kolivas wrote:
On Thursday 19 April 2007 09:59, Con Kolivas wrote:
Since there is so much work currently ongoing with alternative cpu
schedulers, as a standard for comparison with the alternative virtual
deadline fair designs I've addressed a few issues
David Miller [EMAIL PROTECTED] wrote:
As discussed in this thread there might be other ways to a
approach this, but this fix is good for now.
Patch applied, thank you.
Actually I was going to suggest something like this:
[NETLINK]: Kill CB only when socket is unused
Since we can still
Ingo Molnar wrote:
* 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
So, talking about what an (optional) implementation framework might
look like (and which could handle the SOC, FPGA, I2C, and MFD cases
I've looked at):
See patches in following messages ... a preliminary gpio_chip core
for such a framework, plus example support for one SOC family's
On Wed, 2007-04-18 at 20:52 -0500, Florin Iucha wrote:
On Wed, Apr 18, 2007 at 10:11:46AM -0400, Trond Myklebust wrote:
Do you have a copy of wireshark or ethereal on hand? If so, could you
take a look at whether or not any NFS traffic is going between the
client and server once the hang
On Wed, 18 Apr 2007, Ethan Solomita wrote:
Any new ETA? I'm trying to decide whether to go back to your original
patches or wait for the new set. Adding new knobs isn't as important to me as
having something that fixes the core problem, so hopefully this isn't waiting
on them. They could
On Wed, Apr 18, 2007 at 07:48:21AM -0700, Linus Torvalds wrote:
On Wed, 18 Apr 2007, Matt Mackall wrote:
Why is X special? Because it does work on behalf of other processes?
Lots of things do this. Perhaps a scheduler should focus entirely on
the implicit and directed wakeup matrix
On Thu, Apr 19, 2007 at 12:12:14PM +1000, Con Kolivas wrote:
On Thursday 19 April 2007 10:41, Con Kolivas wrote:
On Thursday 19 April 2007 09:59, Con Kolivas wrote:
Since there is so much work currently ongoing with alternative cpu
schedulers, as a standard for comparison with the
On Wed, Apr 18, 2007 at 10:49:45PM +1000, Con Kolivas wrote:
On Wednesday 18 April 2007 22:13, Nick Piggin wrote:
The kernel compile (make -j8 on 4 thread system) is doing 1800 total
context switches per second (450/s per runqueue) for cfs, and 670
for mainline. Going up to 20ms
Russell King wrote:
NAK. This means that you change the list of ports available on the
machine to be limited to only those which are currently open. Utterly
useless for debugging, where you normally want people to dump the
contents of /proc/tty/driver/*.
The original patch was better.
SPIN_LOCK_UNLOCKED cleanup,use __SPIN_LOCK_UNLOCKED instead
Signed-off-by: Milind Arun Choudhary [EMAIL PROTECTED]
---
i2c-pxa.c |2 +-
i2c-s3c2410.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-pxa.c b/drivers/i2c/busses/i2c-pxa.c
SPIN_LOCK_UNLOCKED cleanup,use __SPIN_LOCK_UNLOCKED instead.
Signed-off-by: Milind Arun Choudhary [EMAIL PROTECTED]
---
char/vmlogrdr.c |6 +++---
cio/cmf.c |2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/s390/char/vmlogrdr.c
On 4/18/07, Jiri Slaby [EMAIL PROTECTED] wrote:
johann deneux napsal(a):
Jiri,
Which solution did you chose to implement? From what I remember, we
last discussed Dmitry's idea of specifying an axis for an effect, then
combine several effects to achieve complex effects.
I think you mean
On Wed, Apr 18, 2007 at 10:45:13PM -0400, Trond Myklebust wrote:
On Wed, 2007-04-18 at 20:52 -0500, Florin Iucha wrote:
It seems that my original problem report had a big mistake! There is
no hang, but at some point the write slows down to a trickle (from
40,000 blocks/s to 22 blocks/s) as
Abhijit Bhopatkar wrote:
I just wanted to know weather its worth going forward or we have
better reasons to discount any such direction?
The reason that the wrong pages get swapped out sometimes
could be due to a side effect of the way the swappiness
policy is implemented.
While the VM only
Hi,
On Thursday 19 April 2007 00:25, johann deneux wrote:
On 4/18/07, Jiri Slaby [EMAIL PROTECTED] wrote:
johann deneux napsal(a):
Jiri,
Which solution did you chose to implement? From what I remember, we
last discussed Dmitry's idea of specifying an axis for an effect, then
On Thu, 19 Apr 2007 11:28:37 +0900 izumi [EMAIL PROTECTED] wrote:
Russell King wrote:
NAK. This means that you change the list of ports available on the
machine to be limited to only those which are currently open. Utterly
useless for debugging, where you normally want people to dump
On Thu, 19 Apr 2007 05:18:07 +0200 Nick Piggin [EMAIL PROTECTED] wrote:
And yes, by fairly, I mean fairly among all threads as a base resource
class, because that's what Linux has always done
Yes, there are potential compatibility problems. Example: a machine with
100 busy httpd processes and
I just wanted to know weather its worth going forward or we have
better reasons to discount any such direction?
The reason that the wrong pages get swapped out sometimes
could be due to a side effect of the way the swappiness
policy is implemented.
While the VM only reclaims page cache pages,
Pavel Emelianov wrote:
Peter Zijlstra wrote:
*ugh* /me no like.
The basic premises seems to be that we can track page owners perfectly
(although this patch set does not yet do so), through get/release
It looks like you have examined the patches not very carefully
before concluding this.
Hi,
Here is my patch proposal for detecting possible lockups,
when flush_workqueue caller holds a lock (e.g. rtnl_lock)
also used in work functions.
Regards,
Jarek P.
Signed-off-by: Jarek Poplawski [EMAIL PROTECTED]
---
diff -Nurp 2.6.21-rc6-mm1-/kernel/workqueue.c
701 - 738 of 738 matches
Mail list logo
