On Monday 03 December 2007 22:26:28 Nick Piggin wrote:
> There is one slight downside -- direct block device access and filesystem
> metadata access goes through an extra copy and gets stored in RAM twice.
> However, this downside is only slight, because the real buffercache of the
> device is now
On Dec 4, 2007 3:46 PM, Greg KH <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 04, 2007 at 02:45:47PM +0800, Dave Young wrote:
> > Hi,
> > Does the KOBJ_NAME_LEN really means the limit of kobject name length? seems
> > not . And if it's true, is the KOBJ_NAME_LEN of 20 enough to use?
>
> No, not anymore,
Hi Dave,
On Dec 4, 2007 3:31 AM, Dave Young <[EMAIL PROTECTED]> wrote:
> Kobject_put should be called when kobject register functioin fails, so the
> the kobj ref count touch zero and then the proper cleanup routines will be
> called.
[snip]
> diff -upr linux/drivers/block/pktcdvd.c linux.new/dr
On Tue, Dec 04, 2007 at 01:50:53AM -0500, Robert P. J. Day wrote:
> On Tue, 4 Dec 2007, Dave Young wrote:
>
> > Hi,
> > Does the KOBJ_NAME_LEN really means the limit of kobject name length? seems
> > not . And if it's true, is the KOBJ_NAME_LEN of 20 enough to use?
> >
> > In the kobject_set_name
On Tue, Dec 04, 2007 at 02:45:47PM +0800, Dave Young wrote:
> Hi,
> Does the KOBJ_NAME_LEN really means the limit of kobject name length? seems
> not . And if it's true, is the KOBJ_NAME_LEN of 20 enough to use?
No, not anymore, the kobject name is totally dynamic.
> In the kobject_set_name, the
does anyone know what's happened with the KN list? it seems to have
gone utterly dead for the last day or so.
rday
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http:
On Sat 2007-11-17 11:02:20, Raymano Garibaldi wrote:
> I would like to request a new boot flag/kernel option that would make
> the following scenario possible:
>
> 1) Working on laptop with a live USB distro on a read-only USB stick.
> 2) Suspend laptop.
> 3) Detach USB stick.
>
> 4) Do other thi
On Dec 4, 2007 2:50 PM, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
>
> On Tue, 4 Dec 2007, Dave Young wrote:
>
> > Hi,
> > Does the KOBJ_NAME_LEN really means the limit of kobject name length? seems
> > not . And if it's true, is the KOBJ_NAME_LEN of 20 enough to use?
> >
> > In the kobject_set_n
On Tue, Dec 04, 2007 at 08:01:31AM +0100, Nick Piggin wrote:
> Thanks for the review, I'll post an incremental patch in a sec.
Index: linux-2.6/drivers/block/brd.c
===
--- linux-2.6.orig/drivers/block/brd.c
+++ linux-2.6/drivers/blo
On Mon, Dec 03, 2007 at 10:29:03PM -0800, Andrew Morton wrote:
> On Tue, 4 Dec 2007 05:26:28 +0100 Nick Piggin <[EMAIL PROTECTED]> wrote:
> >
> > There is one slight downside -- direct block device access and filesystem
> > metadata access goes through an extra copy and gets stored in RAM twice.
>
Hi all,
Could anyone give some ideas of future pending works which are needed
on the linux kernel?
Thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Ple
On Tue, 4 Dec 2007, Dave Young wrote:
> Hi,
> Does the KOBJ_NAME_LEN really means the limit of kobject name length? seems
> not . And if it's true, is the KOBJ_NAME_LEN of 20 enough to use?
>
> In the kobject_set_name, the limit is 1024. Looks like either the comment or
> the code should be upda
Hi,
Does the KOBJ_NAME_LEN really means the limit of kobject name length? seems not
. And if it's true, is the KOBJ_NAME_LEN of 20 enough to use?
In the kobject_set_name, the limit is 1024. Looks like either the comment or
the code should be updated.
/**
* kobject_set_name - Set the name
On Mon, 2007-12-03 at 11:05 +0100, Ingo Molnar wrote:
> * Zhang, Yanmin <[EMAIL PROTECTED]> wrote:
>
> > Although no source codes of volanoMark, I suspect it calls
> > Thread.sched. volanoMark is a kind of chatroom benchmark. When a
> > client sends out a message, server will send the message to
On Tue, Dec 04, 2007 at 01:24:40PM +0900, Simon Horman wrote:
> On Mon, Dec 03, 2007 at 10:43:45PM -0500, Amos Waterland wrote:
> > The difference between ip=off and ip=::off has been a cause of much
> > confusion. Document how each behaves, and do not contradict ourselves
> > by saying that "
Applied to suspend branch.
thanks,
-len
On Monday 03 December 2007 19:11, Rafael J. Wysocki wrote:
> [This is a replacement for
> freezer-fix-jffs2-garbage-collector-freezing-issue.patch]
> ---
> From: Rafael J. Wysocki <[EMAIL PROTECTED]>
>
> Fix breakage caused by commit d5d8c5976d6adeddb8208c
On Tue, 4 Dec 2007 05:26:28 +0100 Nick Piggin <[EMAIL PROTECTED]> wrote:
> Hi,
>
> This is my proposal for a (hopefully) backwards compatible rd driver.
> The motivation for me is not pressing, except that I have this code
> sitting here that is either going to rot or get merged. I'm happy to
> m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
KaiGai Kohei wrote:
> Serge,
>
> Please tell me the meanings of the following condition.
>
>> diff --git a/security/commoncap.c b/security/commoncap.c
>> index 3a95990..cb71bb0 100644
>> --- a/security/commoncap.c
>> +++ b/security/commoncap.c
>> @@
The current pci_assign_unassigned_resources() code doesn't work properly
on 32 bits platforms with 64 bits resources. The main reason is the use
of unsigned long in various places instead of resource_size_t.
This fixes it, along with some tricks to avoid casting to 64 bits on
platforms that don't
The commit fa13a5a1f25f671d084d8884be96fc48d9b68275 (sched: restore
deterministic CPU accounting on powerpc), unconditionally calls
update_process_tick() in system context. In the deterministic accounting case
this is the correct thing to do. However, in the non-deterministic accounting
case we n
We should have one week between -rc releases, but I was gone for a week
over thanksgiving (as were some other kernel developers), so this one is a
bit late. It's been almost the rule rather than the exception, but I
promise I'll be better...
Anyway, there aren't a lot of exciting changes here,
--- Jiri Slaby <[EMAIL PROTECTED]> wrote:
> On 12/03/2007 07:39 PM, Casey Schaufler wrote:
> > From: Casey Schaufler <[EMAIL PROTECTED]>
> >
> > Clean out unnecessary mutex initializations for Smack list locks.
> > Once this is done, there is no need for them to be shared among
> > multiple file
The commit fa13a5a1f25f671d084d8884be96fc48d9b68275, unconditionally calls
update_process_tick() in system context. In the deterministic accounting case
this is the correct thing to do. However, in the non-deterministic accounting
case we need to not do this, and results in the time accounted as
Serge,
Please tell me the meanings of the following condition.
diff --git a/security/commoncap.c b/security/commoncap.c
index 3a95990..cb71bb0 100644
--- a/security/commoncap.c
+++ b/security/commoncap.c
@@ -133,6 +119,12 @@ int cap_capset_check (struct task_struct *target,
kernel_cap_t *effec
Hi,
This is my proposal for a (hopefully) backwards compatible rd driver.
The motivation for me is not pressing, except that I have this code
sitting here that is either going to rot or get merged. I'm happy to
make myself maintainer of this code, but if any real block device
driver writer would l
On Tue, Dec 04, 2007 at 01:24:40PM +0900, Simon Horman wrote:
> On Mon, Dec 03, 2007 at 10:43:45PM -0500, Amos Waterland wrote:
> > The difference between ip=off and ip=::off has been a cause of much
> > confusion. Document how each behaves, and do not contradict ourselves
> > by saying that "
Hi,
I just wanted to let you know that I'll have picked up the early
firewire patch again and cleaned it up very much so that it should
be ready to submit it and but it on the patch-submission road.
What's left to do is to write some HOWTO like Stefan describes
below, but I'll try to get that
On Mon, Dec 03, 2007 at 10:43:45PM -0500, Amos Waterland wrote:
> The difference between ip=off and ip=::off has been a cause of much
> confusion. Document how each behaves, and do not contradict ourselves
> by saying that "off" is the default when in fact "any" is the default
> and is descibe
Jeff Garzik wrote:
> Neil Brown wrote:
>> I've been looking at use BIO_RW_FAILFAST in md/raid to improve
>> handling of some error cases.
>>
>> This is particularly significant for the DASD driver (s390 specific).
>> I believe it uses optic fibre to connect to the drives. When one of
>> these pa
On Tue, Dec 04, 2007 at 11:50:55AM +0800, Wang Chen wrote:
>
> > #include
> > #include
> > +#include
>
> It's no need to include smp.h?
We need it for smp_processor_id. Well we needed it before too but
there's probably some implicit inclusion which has made it work.
It's better to declare t
Herbert Xu said the following on 2007-12-3 21:17:
> On Mon, Dec 03, 2007 at 10:54:35PM +1100, Herbert Xu wrote:
> diff --git a/include/net/snmp.h b/include/net/snmp.h
> index ea206bf..9444b54 100644
> --- a/include/net/snmp.h
> +++ b/include/net/snmp.h
> @@ -23,6 +23,7 @@
>
> #include
> #inclu
Neil Brown wrote:
I've been looking at use BIO_RW_FAILFAST in md/raid to improve
handling of some error cases.
This is particularly significant for the DASD driver (s390 specific).
I believe it uses optic fibre to connect to the drives. When one of
these paths is unplugged, IO requests will blo
The difference between ip=off and ip=::off has been a cause of much
confusion. Document how each behaves, and do not contradict ourselves
by saying that "off" is the default when in fact "any" is the default
and is descibed as being so lower in the file.
Signed-off-by: Amos Waterland <[EMAIL
The cycles/usecs conversion macros should be dependent on
CONFIG_EVENT_TRACE instead of CONFIG_LATENCY_TIMING.
Signed-off-by: Kevin Hilman <[EMAIL PROTECTED]>
--- a/include/asm-arm/timex.h
+++ b/include/asm-arm/timex.h
@@ -18,7 +18,7 @@ typedef unsigned long cycles_t;
#ifndef mach_read_cycles
On Tuesday December 4, [EMAIL PROTECTED] wrote:
> On Tue, Dec 04, 2007 at 11:14:12AM +1100, Neil Brown wrote:
> > On Tuesday December 4, [EMAIL PROTECTED] wrote:
> > > Neil,
> > >
> > > I just upgraded an ia64 (Altix, 16k page size) test box to 2.6.24-rc3
> > > from 2.6.23 and I get it panicing on
I've been looking at use BIO_RW_FAILFAST in md/raid to improve
handling of some error cases.
This is particularly significant for the DASD driver (s390 specific).
I believe it uses optic fibre to connect to the drives. When one of
these paths is unplugged, IO requests will block until an operato
On Tue, Dec 04, 2007 at 11:14:12AM +1100, Neil Brown wrote:
> On Tuesday December 4, [EMAIL PROTECTED] wrote:
> > Neil,
> >
> > I just upgraded an ia64 (Altix, 16k page size) test box to 2.6.24-rc3
> > from 2.6.23 and I get it panicing on boot in the umem driver.
>
> Cool - someone is using umem!
On Tuesday 04 December 2007 11:30, David Schwartz wrote:
> Perhaps it might be possible to scan for the task at the same static
> priority level that is ready-to-run but last in line among other
> ready-to-run tasks and put it after that task?
Nice level versus posix static priority level debate
Fix "warning: Using plain integer as NULL pointer".
Convert 'x < y ? x : y' to use min() instead.
Signed-off-by: Richard Knutsson <[EMAIL PROTECTED]>
Signed-off-by: Hans Verkuil <[EMAIL PROTECTED]>
---
Compile-tested on i386 with "allyesconfig" and "allmodconfig".
Resend, since the 'Remove a gcc-2
On Mon, 3 Dec 2007 23:34:26 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> On Monday, 3 of December 2007, Andrew Morton wrote:
> > On Sun, 2 Dec 2007 21:33:23 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
> > wrote:
> >
> > > On Saturday, 1 of December 2007, Pavel Machek wrote:
> > > > H
Phillip Susi wrote:
> Tejun Heo wrote:
>> Surprise, surprise. There's no way to tell whether the controller
>> raised interrupt or not if command is not in progress. As I said
>> before, there's no IRQ pending bit. While processing commands, you can
>> tell by looking at other status registers b
Kobject_put should be called when kobject register functioin fails, so the the
kobj ref count touch zero and then the proper cleanup routines will be called.
Signed-off-by: Dave Young <[EMAIL PROTECTED]>
---
drivers/block/pktcdvd.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
dif
On Tue, Dec 04, 2007 at 08:55:13AM +0800, Shaohua Li wrote:
>
> On Mon, 2007-12-03 at 18:02 +0100, Rene Herman wrote:
> > On 30-11-07 23:22, Rene Herman wrote:
> >
> > > On 30-11-07 14:14, Chris Holvenstot wrote:
> > >
> > >> For what it is worth I too have seen this problem this morning and it
Jan Engelhardt wrote:
> Repository overview.
> CGIT: http://cgit.freedesktop.org/
> GITWEB: http://git.kernel.org/
Why not compare more equal pages? freedesktop.org also runs gitweb:
http://gitweb.freedesktop.org
>
> Remarks:
> cgit is lacking the links "shortlog", "log"
On Monday 03 December 2007 22:37, Ingo Molnar wrote:
> * Nick Piggin <[EMAIL PROTECTED]> wrote:
> > > given how poorly sched_yield() is/was defined the only "compatible"
> > > solution would be to go back to the old yield code.
> >
> > While it is technically allowed to do anything with SCHED_OTHER
On Mon, 2007-12-03 at 18:02 +0100, Rene Herman wrote:
> On 30-11-07 23:22, Rene Herman wrote:
>
> > On 30-11-07 14:14, Chris Holvenstot wrote:
> >
> >> For what it is worth I too have seen this problem this morning and it
> >> DOES appear to be new (in contrast to a previous comment)
> >>
> >> T
On Mon, 2007-12-03 at 23:45 +0100, Bodo Eggert wrote:
> Jon Masters <[EMAIL PROTECTED]> wrote:
> > On Thu, 2007-11-29 at 11:11 -0800, Ray Lee wrote:
> >> On Nov 29, 2007 10:56 AM, Jon Masters <[EMAIL PROTECTED]> wrote:
> >> > On Thu, 2007-11-29 at 10:40 -0800, Ray Lee wrote:
> >> > > On Nov 29, 20
> * Mark Lord <[EMAIL PROTECTED]> wrote:
> > Ack. And what of the suggestion to try to ensure that a yielding task
> > simply not end up as the very next one chosen to run? Maybe by
> > swapping it with another (adjacent?) task in the tree if it comes out
> > on top again?
> we did that too fo
On Tuesday 04 December 2007 09:33, Ingo Molnar wrote:
> * Mark Lord <[EMAIL PROTECTED]> wrote:
> >> heh, thanks :) For which workload does it make the biggest difference
> >> for you? (and compared to what other scheduler you used before?
> >> 2.6.22?)
> >
> > ..
> >
> > Heh.. I'm just a very unsop
On Tuesday December 4, [EMAIL PROTECTED] wrote:
> Neil,
>
> I just upgraded an ia64 (Altix, 16k page size) test box to 2.6.24-rc3
> from 2.6.23 and I get it panicing on boot in the umem driver.
Cool - someone is using umem! And even testing it. Thanks!
A quick look shows a probable NULL deref.
On Mon, 3 December 2007 01:57:02 +0100, Jörn Engel wrote:
>
> After an eternity of compile time, this config does generate some useful
> output. qemu is not to blame.
Or is it? The output definitely looks suspicious. Large amounts of
code get processed within a microsecond, while update_wall_t
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > > Er, it won't play well if that happen when tasks are frozen for
> > > suspend.
> >
> > right now any suspend attempt times out after 20 seconds:
> >
> > $ grep TIMEOUT kernel/power/process.c
> > #define TIMEOUT (20 * HZ)
> > en
On Mon, 3 Dec 2007 15:53:17 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Sun, 2 Dec 2007 20:43:46 +0100 (CET)
> Thomas Bogendoerfer <[EMAIL PROTECTED]> wrote:
>
> > New serial driver for SC2681/SC2691 uarts. Older SNI RM400 machines
> > are using these chips for onboard serial ports.
> >
On Sun, 2 Dec 2007 20:43:46 +0100 (CET)
Thomas Bogendoerfer <[EMAIL PROTECTED]> wrote:
> New serial driver for SC2681/SC2691 uarts. Older SNI RM400 machines are
> using these chips for onboard serial ports.
>
Little things...
> --- /dev/null
> +++ b/drivers/serial/sc26xx.c
> @@ -0,0 +1,757 @@
[This is a replacement for
freezer-fix-jffs2-garbage-collector-freezing-issue.patch]
---
From: Rafael J. Wysocki <[EMAIL PROTECTED]>
Fix breakage caused by commit d5d8c5976d6adeddb8208c240460411e2198b393
"freezer: do not send signals to kernel threads" in
jffs2_garbage_collect_thread() that assume
On Saturday, 1 of December 2007, Rafael J. Wysocki wrote:
> On Friday, 30 of November 2007, Pete MacKay wrote:
[--snip--]
> ---
> Subject: Freezer: Fix JFFS2 garbage collector freezing issue
> From: Rafael J. Wysocki <[EMAIL PROTECTED]>
>
> Fix breakage caused by commit d5d8c5976d6adeddb8208c24046
> -Original Message-
> From: Mark Fasheh [mailto:[EMAIL PROTECTED]
> Sent: den 3 december 2007 22:34
> To: Joakim Tjernlund
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: what happened to RELATIME?
>
> On Mon, Dec 03, 2007 at 09:16:15PM +0100, Joakim Tjernlund wrote:
> > Looking in 2.6
On Mon, Dec 03, 2007 at 03:13:49PM -0800, Andrew Morton wrote:
> On Mon, 3 Dec 2007 14:47:22 -0800
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > Does this fix?
>
> Slightly more elaborate version
Yes, this patch does eliminate the problem. Without it, no write can
complete, and with it I hav
Please pull from:
master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.24.git
Which contains:
Nobuhiro Iwamatsu (2):
sh: Fix PCI IO space base address of SH7780.
sh: Support PCI IO access of SH7780 base boards.
arch/sh/drivers/pci/ops-r7780rp.c |4 ++--
arch/sh/dri
On Sun, 2 Dec 2007 14:48:42 +0100
Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Sun, Dec 02, 2007 at 05:43:39PM +0900, Tetsuo Handa wrote:
> >
> > mm/slub.c exports ksize(), but mm/slob.c and mm/slab.c don't. I don't know
> > why.
> >...
>
> That's due to the fact that my patch to remove this unu
Andrew Morton <[EMAIL PROTECTED]> writes:
>> +#ifdef CONFIG_SYSCTL
>> static ctl_table fs_dqstats_table[] = {
>> {
>> .ctl_name = FS_DQ_LOOKUPS,
>> @@ -1918,6 +1919,7 @@ static ctl_table sys_table[] = {
>> },
>> { .ctl_name = 0 },
>> };
>> +#endif
>>
>> stati
Ray Lee wrote:
Hey there Larry, all,
git blame fingered commit id efe870f9 (from Larry) for adding a couple
of fairly harmless looking messages to
net/ieee80211/softmac/ieee80211softmac_wx.c . The problem is that one
of them is clogging up my syslog at the tune of once a second or so
("SoftMAC:
On Mon, Dec 03, 2007 at 02:47:22PM -0800, Andrew Morton wrote:
> On Mon, 3 Dec 2007 16:38:37 -0500
> "Ed L. Cashin" <[EMAIL PROTECTED]> wrote:
...
> > It appears that the fbc->counters pointer is NULL.
>
> Does this fix?
>
> --- a/drivers/block/aoe/aoeblk.c~a
> +++ a/drivers/block/aoe/aoeblk.c
>
Alan Stern wrote, On 12/03/2007 04:08 PM:
> On Mon, 3 Dec 2007, Jarek Poplawski wrote:
>
>>> System sleep start:
>>> down_read(notifier-chain rwsem);
>>> call the notifier routine
>>> down_write(&system_sleep_in_progress_rwsem);
>>> up_read(
On 12/03/2007 07:39 PM, Casey Schaufler wrote:
> From: Casey Schaufler <[EMAIL PROTECTED]>
>
> Clean out unnecessary mutex initializations for Smack list locks.
> Once this is done, there is no need for them to be shared among
> multiple files, so pull them out of the header file and put them
> in
On Mon, 3 Dec 2007 14:47:22 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
> Does this fix?
Slightly more elaborate version
- handle errors
- don't do illegal things under spinlock
- clean up error unwinding
---
a/drivers/block/aoe/aoeblk.c~aoe-properly-initialise-the-request_queues-backing_
Hi Bartlomiej,
On Sat, 1 Dec 2007 23:53:05 +0100, Bartlomiej Zolnierkiewicz <[EMAIL
PROTECTED]> wrote:
> On Saturday 01 December 2007, Kiyoshi Ueda wrote:
> > This patch converts "normal" parts of ide to use blk_end_request().
> >
> > Signed-off-by: Kiyoshi Ueda <[EMAIL PROTECTED]>
> > Signed-of
> Given a fast low-latency solid state drive, would it ever be beneficial
> to simply wait in the kernel for synchronous read/write calls to
> complete? The idea is that you could avoid at least two task context
> switches, and if the data access can be completed at less cost than
> those cont
Over on comp.os.linux.development.system someone asked an interesting
question, and I thought I'd mention it here.
Given a fast low-latency solid state drive, would it ever be beneficial
to simply wait in the kernel for synchronous read/write calls to
complete? The idea is that you could av
On Mon, Dec 03, 2007 at 06:01:40PM +0530, Supriya Kannery wrote:
> Nick Piggin wrote:
> >On Thu, Nov 29, 2007 at 02:45:23PM -0500, Chuck Ebbert wrote:
> >
> >>Original report: https://bugzilla.redhat.com/show_bug.cgi?id=404201
> >>
> >>The test case below, taken from the LTP test code, prints -1
Hi Geert,
On Sun, 2 Dec 2007 10:34:56 +0100 (CET), Geert Uytterhoeven <[EMAIL PROTECTED]>
wrote:
> On Fri, 30 Nov 2007, Kiyoshi Ueda wrote:
> > This patch converts ps3disk to use blk_end_request().
> ^^^
> Patch subject and description are inconsis
On Mon, 2007-12-03 at 18:02 +0100, Rene Herman wrote:
> On 30-11-07 23:22, Rene Herman wrote:
>
> > On 30-11-07 14:14, Chris Holvenstot wrote:
> >
> >> For what it is worth I too have seen this problem this morning and it
> >> DOES appear to be new (in contrast to a previous comment)
> >>
> >> T
Hi Bartlomiej,
On Sat, 1 Dec 2007 23:42:51 +0100, Bartlomiej Zolnierkiewicz <[EMAIL
PROTECTED]> wrote:
> On Saturday 01 December 2007, Kiyoshi Ueda wrote:
> > This patch converts ide-cd (cdrom_newpc_intr()) to use blk_end_request().
> >
> > ide-cd (cdrom_newpc_intr()) has some tricky behaviors b
On Mon, 3 Dec 2007 16:38:37 -0500
"Ed L. Cashin" <[EMAIL PROTECTED]> wrote:
> > --- lx/lib/percpu_counter.c.200711302007-12-03 15:43:19.0
> > -0500
> > +++ lx/lib/percpu_counter.c 2007-12-03 15:47:38.0 -0500
> > @@ -33,7 +33,9 @@ void __percpu_counter_add(struct perc
Jon Masters <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-11-29 at 11:11 -0800, Ray Lee wrote:
>> On Nov 29, 2007 10:56 AM, Jon Masters <[EMAIL PROTECTED]> wrote:
>> > On Thu, 2007-11-29 at 10:40 -0800, Ray Lee wrote:
>> > > On Nov 29, 2007 9:36 AM, Alan Cox <[EMAIL PROTECTED]> wrote:
>> > > > > close
Hi Kenji-san,
* Kenji Kaneshige <[EMAIL PROTECTED]>:
> Hi Alex-san,
>
>>> On my system, hotplug slots themselves can be added, removed
>>> and replaced with the ohter type of I/O box.
Are you talking about some sort of I/O cabinet/chassis that you
can attach to the actual computer? Can the I/O e
* Mark Lord <[EMAIL PROTECTED]> wrote:
>> heh, thanks :) For which workload does it make the biggest difference
>> for you? (and compared to what other scheduler you used before?
>> 2.6.22?)
> ..
>
> Heh.. I'm just a very unsophisticated desktop user, and I like it when
> Thunderbird and Firef
On Monday, 3 of December 2007, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> > > This feature will save one full reporter-developer round-trip during
> > > investigation of a significant number of bug reports.
> > >
> > > It might be more practical if it were to dump
On Monday, 3 of December 2007, David Chinner wrote:
> On Sun, Dec 02, 2007 at 09:06:19AM -0800, Avuton Olrich wrote:
> > Adding xfs to CC
> >
> > On Dec 2, 2007 9:02 AM, Avuton Olrich <[EMAIL PROTECTED]> wrote:
> > > Hello,
> > >
> > > 2.6.23.8 just crashed here, it had been up 8 days and suspende
On Monday 03 December 2007 05:50:38 Cyrill Gorcunov wrote:
> This patch does fix missed mutex unlock. Please see it attached.
> (Can't send it as a plain text patch - have only IE based mail access)
>
> Cyrill
Acked-by: Michael Wu <[EMAIL PROTECTED]>
Thanks,
-Michael Wu
signature.asc
Description
Ingo Molnar wrote:
* Mark Lord <[EMAIL PROTECTED]> wrote:
Ack. And what of the suggestion to try to ensure that a yielding task
simply not end up as the very next one chosen to run? Maybe by
swapping it with another (adjacent?) task in the tree if it comes out
on top again?
we did that to
On Monday, 3 of December 2007, Andrew Morton wrote:
> On Sun, 2 Dec 2007 21:33:23 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
> wrote:
>
> > On Saturday, 1 of December 2007, Pavel Machek wrote:
> > > Hi!
> > >
> > > > 2.6.24-rc3-mm2 (which will be released if it boots on two more machines
> >
On Mon, Dec 03, 2007 at 02:31:40PM +0100, Jan Glauber wrote:
> Hi Herbert,
>
> commit 788fefa33b0b50581585925c53c230a36af35d0e in cryptodev breaks hmac
> on s390 du to the usage of sg_chain():
>
> static inline void sg_chain(struct scatterlist *prv, unsigned int prv_nents,
>
* Mark Lord <[EMAIL PROTECTED]> wrote:
> Ack. And what of the suggestion to try to ensure that a yielding task
> simply not end up as the very next one chosen to run? Maybe by
> swapping it with another (adjacent?) task in the tree if it comes out
> on top again?
we did that too for quite s
Should be applied after the
"Add HAVE_KPROBES" patch.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: Haavard Skinnemoen <[EMAIL PROTECTED]>
CC: Andrew Morton <[EMAIL PROTECTED]>
---
arch/avr32/Kconfig |1 +
1 file changed, 1 insertion(+)
Index: linux-2.6-lttng/arch/avr32/Kconfig
=
> All ptrace cleanup patches from Roland were posted by him to lkml, and
> we picked them up from there. Review is ongoing, Roland replied to all
> feedback with more patches, and those were integrated as well. Final
> upstream merging of this depends on more review and test results (as
> usual
Quoting : Haavard Skinnemoen <[EMAIL PROTECTED]>
Mathieu, I want to get oprofile support queued up for 2.6.25, and
since I don't see any signs that the Kconfig.instrumentation removal
patches are going in any time soon, I'm going to turn things around
and apply these two patches to my tree.
This
> You could write an equally effcient kernel in languages like C++,
> using C++ abstractions as a high level organization, where
It's very very hard to generate good C code because of the numerous ways
objects get temporarily created, and the week aliasing rules (as with C).
There are reasons tha
Hi guys,
Can anybody tell me how to find the mapping of PCI PnP ids for those
built-in modules(linked into kernel). AFAICT, PnP id and module mapping
could be found in /lib/modules/`uname -r`/modules.pcimap for the loadable
modules. I think there should be a table or list for the mapping between
Ingo Molnar wrote:
* Mark Lord <[EMAIL PROTECTED]> wrote:
That's not the same thing at all. I think that David is suggesting
that the reinsertion logic should pretend that the task used up all of
the CPU time it was offered in the slot leading up to the
sched_yield() call.
we have tried thi
On Mon, 3 Dec 2007, Pavel Machek wrote:
> On Mon 2007-12-03 22:45:06, Guennadi Liakhovetski wrote:
> > On Sun, 2 Dec 2007, Pavel Machek wrote:
>
> > > > CR0: 8005003b CR2: 081dcf88 CR3: 07e46000 CR4: 02d0
> > > > DR0: DR1: DR2: DR3:
> > > > DR6: 0ff0 DR
* Andi Kleen <[EMAIL PROTECTED]> wrote:
> Ingo Molnar <[EMAIL PROTECTED]> writes:
>
> > * Andi Kleen <[EMAIL PROTECTED]> wrote:
> >
> >> Just don't wait for that. utrace doesn't seem to have any concrete
> >> plans to merge any time soon AFAIK[1] and it would be a shame to delay
> >> an useful
On Mon 2007-12-03 22:45:06, Guennadi Liakhovetski wrote:
> On Sun, 2 Dec 2007, Pavel Machek wrote:
>
> > > I compiled a .24-ish kernel for it with CONFIG_NO_HZ and
> > > CONFIG_HIGH_RES_TIMERS. To get the system boot at least sometimes I have
> > > to specify nohz=off. Then I get
> >
> > Try hi
* Mark Lord <[EMAIL PROTECTED]> wrote:
> That's not the same thing at all. I think that David is suggesting
> that the reinsertion logic should pretend that the task used up all of
> the CPU time it was offered in the slot leading up to the
> sched_yield() call.
we have tried this too, and th
On Sun, 2 Dec 2007, Pavel Machek wrote:
> > I compiled a .24-ish kernel for it with CONFIG_NO_HZ and
> > CONFIG_HIGH_RES_TIMERS. To get the system boot at least sometimes I have
> > to specify nohz=off. Then I get
>
> Try highres=off, too... Hehe, and even idle=poll might help.
Ok, for now I'v
Chris Friesen wrote:
David Schwartz wrote:
Chris Friesen wrote:
..
The problem is where do we insert the task that is yielding? CFS is
based around a tree structure ordered by time.
We put it exactly where we would have when its timeslice ran out. If
we can
reward it a little bit, that's
On Mon, Dec 03, 2007 at 04:00:05PM -0500, Ed L. Cashin wrote:
...
> I'll keep looking at this, but at a glance it looks like the cpu
> number is valid, because I don't trip a BUG_ON when I make the change
> below (the badval variable is noise, sorry).
>
> --- lx/lib/percpu_counter.c.20071130
On Fri, 30 Nov 2007 16:02:50 +0300
Pavel Emelyanov <[EMAIL PROTECTED]> wrote:
> This includes the tables themselves and the call to the
> register_sysctl_table(). Since this call is done from the __init
> call, I hope this is OK to keep the #ifdef inside the function,
> rather than making proper
On Mon, 3 Dec 2007 22:13:53 +0100, Willy Tarreau <[EMAIL PROTECTED]> wrote:
...
>
> It just depends how many times a second it happens. For instance, consider
> this trivial loop (fct is a two-function array which just return 1 or 2) :
>
> i = 0;
> for (j = 0; j < (1 << 28); j++)
Neil,
I just upgraded an ia64 (Altix, 16k page size) test box to 2.6.24-rc3
from 2.6.23 and I get it panicing on boot in the umem driver.
[ 55.499300] v2.3 : Micro Memory(tm) PCI memory board block driver
[ 55.519331] ACPI: Unable to derive IRQ for device 0006:00:01.0
[ 55.528294] ACPI: PCI
1 - 100 of 305 matches
Mail list logo
