On 23/03/07, Nick Piggin <[EMAIL PROTECTED]> wrote:
On Thu, Mar 22, 2007 at 06:40:41PM -0700, Linus Torvalds wrote:
>
> [ Ok, I think it's those timers again...
>
> Ingo: let me just state how *happy* I am that I told you off when you
> wanted to merge the hires timers and NO_HZ before 2.6.20
On Thu, 22 Mar 2007 23:52:05 -0700 (PDT) Christoph Lameter <[EMAIL PROTECTED]>
wrote:
> On Thu, 22 Mar 2007, Andrew Morton wrote:
>
> > On Thu, 22 Mar 2007 23:28:41 -0700 (PDT) Christoph Lameter <[EMAIL
> > PROTECTED]> wrote:
> >
> > > 1. Proven code from the IA64 arch.
> > >
> > > The meth
Pekka J Enberg a écrit :
(Please inline patches to the mail, makes it easier to review.)
On Thu, 22 Mar 2007, Eric Dumazet wrote:
Some NUMA machines have a big MAX_NUMNODES (possibly 1024), but fewer possible
nodes. This patch dynamically sizes the 'struct kmem_cache' to allocate only
needed sp
On Fri, 2007-03-23 at 08:27 +0100, Jean Delvare wrote:
> Hi Bryan,
>
> On Fri, 23 Mar 2007 13:46:57 +0800, Wu, Bryan wrote:
> > Changlogs:
> >
> > a) Fixed issues according to Jean's review.
> > b) Add MAINTAINS infomation
> > c) add I2C_HW_B_BLACKFIN to i2c-id.h
>
> I2C_HW_B_* is traditionally
Hi Bryan,
On Fri, 23 Mar 2007 13:46:57 +0800, Wu, Bryan wrote:
> Changlogs:
>
> a) Fixed issues according to Jean's review.
> b) Add MAINTAINS infomation
> c) add I2C_HW_B_BLACKFIN to i2c-id.h
I2C_HW_B_* is traditionally used for drivers built on top of the
i2c-algo-bit driver, which isn't the c
On Thu, 2007-03-22 at 12:45 +0100, Sam Ravnborg wrote:
> On Thu, Mar 22, 2007 at 09:09:42PM +1100, Rusty Russell wrote:
> > It also fixes the remaining warnings, except one. The code in
> > modpost.c which needs to be taught that it's legal to link from
> > .paravirtprobe to .init.text is horrible
On Thu, 2007-03-22 at 16:59 +0100, Sébastien Dugué wrote:
> Rename boot_gdt_table to boot_gdt to avoid the duplicate
> T(able).
>
> Signed-off-by: Sébastien Dugué <[EMAIL PROTECTED]>
>
> ---
> arch/i386/kernel/head.S |9 -
> arch/i386/kernel/trampoline.S | 12 ++--
>
On Fri, 23 Mar 2007 07:51:47 +0100 Blaisorblade <[EMAIL PROTECTED]> wrote:
> On Thursday 22 March 2007 22:44, [EMAIL PROTECTED] wrote:
> > The patch titled
> > uml: mreate arch.h
> ^
> > has been added to the -mm tree. Its filename is
> > uml-create-archh.patch
> mreate? I've a
* Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> >> > BUG: at kernel/fork.c:1033 copy_process()
> >>
> >> thanks Michal - this is a real bug that affects upstream too. Find
> >> the fix below - i've test-booted it and it fixes the warning.
> >
> > Problem is fixed, thanks.
>
> BTW. It seems th
(Please inline patches to the mail, makes it easier to review.)
On Thu, 22 Mar 2007, Eric Dumazet wrote:
> Some NUMA machines have a big MAX_NUMNODES (possibly 1024), but fewer possible
> nodes. This patch dynamically sizes the 'struct kmem_cache' to allocate only
> needed space.
>
> I moved node
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
upstream-linus
to receive the following updates:
drivers/net/Kconfig | 25 ++--
drivers/net/cxgb3/common.h | 15 ++
drivers/net/cxgb3/cx
On Thursday 22 March 2007 22:44, [EMAIL PROTECTED] wrote:
> The patch titled
> uml: mreate arch.h
^
> has been added to the -mm tree. Its filename is
> uml-create-archh.patch
mreate? I've also seen this in all other patches of this batch (examples
below), and both Jeff's orig
Prepare the raid5 implementation to use async_tx for running stripe
operations:
* biofill (copy data into request buffers to satisfy a read request)
* compute block (generate a missing block in the cache from the other
blocks)
* prexor (subtract existing data as part of the read-modify-write proces
handle_stripe sets STRIPE_OP_CHECK to request a check operation in
raid5_run_ops. If raid5_run_ops is able to perform the check with a
dma engine the parity will be preserved in memory removing the need to
re-read it from disk, as is necessary in the synchronous case.
'Repair' operations re-use t
Use raid5_run_ops to carry out the memory copies for a raid5 read request.
Signed-off-by: Dan Williams <[EMAIL PROTECTED]>
---
drivers/md/raid5.c | 40 +++-
1 files changed, 15 insertions(+), 25 deletions(-)
diff --git a/drivers/md/raid5.c b/drivers/md/raid
Adds the platform device definitions and the architecture specific
support routines (i.e. register initialization and descriptor formats) for the
iop-adma driver.
Changelog:
* added 'descriptor pool size' to the platform data
* add base support for buffer sizes larger than 16MB (hw max)
* build er
handle_stripe sets STRIPE_OP_COMPUTE_BLK to request servicing from
raid5_run_ops. It also sets a flag for the block being computed to let
other parts of handle_stripe submit dependent operations. raid5_run_ops
guarantees that the compute operation completes before any dependent
operation starts.
async_tx is an api to describe a series of bulk memory
transfers/transforms. When possible these transactions are carried out by
asynchrounous dma engines. The api handles inter-transaction dependencies
and hides dma channel management from the client. When a dma engine is not
present the transa
This is a driver for the iop DMA/AAU/ADMA units which are capable of pq_xor,
pq_update, pq_zero_sum, xor, dual_xor, xor_zero_sum, fill, copy+crc, and copy
operations.
Changelog:
* fixed a slot allocation bug in do_iop13xx_adma_xor that caused too few
slots to be requested eventually leading to dat
Adds the platform device definitions and the architecture specific support
routines (i.e. register initialization and descriptor formats) for the
iop-adma driver.
Changelog:
* add support for > 1k zero sum buffer sizes
* added dma/aau platform devices to iq80321 and iq80332 setup
* fixed the calcu
replaced by raid5_run_ops
Signed-off-by: Dan Williams <[EMAIL PROTECTED]>
---
drivers/md/raid5.c | 124
1 files changed, 0 insertions(+), 124 deletions(-)
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 0be26c2..062df02 100644
---
The parity calculation for an expansion operation is the same as the
calculation performed at the end of a write with the caveat that all blocks
in the stripe are scheduled to be written. An expansion operation is
identified as a stripe with the POSTXOR flag set and the BIODRAIN flag not
set.
The
handle_stripe now only updates the state of stripes. All execution of
operations is moved to raid5_run_ops.
Signed-off-by: Dan Williams <[EMAIL PROTECTED]>
---
drivers/md/raid5.c | 68
1 files changed, 10 insertions(+), 58 deletions(-)
dif
handle_stripe sets STRIPE_OP_PREXOR, STRIPE_OP_BIODRAIN, STRIPE_OP_POSTXOR
to request a write to the stripe cache. raid5_run_ops is triggerred to run
and executes the request outside the stripe lock.
Signed-off-by: Dan Williams <[EMAIL PROTECTED]>
---
drivers/md/raid5.c | 152 +
On Thu, 22 Mar 2007, Andrew Morton wrote:
> On Thu, 22 Mar 2007 23:28:41 -0700 (PDT) Christoph Lameter <[EMAIL
> PROTECTED]> wrote:
>
> > 1. Proven code from the IA64 arch.
> >
> > The method used here has been fine tuned for years and
> > is NUMA aware. It is based on the knowledge tha
Signed-off-by: Dan Williams <[EMAIL PROTECTED]>
---
arch/arm/Kconfig |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index e7baca2..74077e3 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -997,6 +997,8 @@ source "drivers/mmc/Kc
Each stripe has three flag variables to reflect the state of operations
(pending, ack, and complete).
-pending: set to request servicing in raid5_run_ops
-ack: set to reflect that raid5_runs_ops has seen this request
-complete: set when the operation is complete and it is ok for handle_stripe5
to c
The async_tx api provides methods for describing a chain of asynchronous
bulk memory transfers/transforms with support for inter-transactional
dependencies. It is implemented as a dmaengine client
that smooths over the details of different hardware offload engine
implementations. Code that is wri
The following patch set implements the async_tx api and modifies
md-raid5 to issue memory copies and xor calculations asynchronously.
Async_tx is an extension of the existing dmaengine interface in the
kernel. Async_tx allows kernel code to utilize application specific
acceleration engines when pr
On Thursday 22 March 2007 17:06, Jeff Dike wrote:
> This patch moves all the the symbols defined in um_arch.c, which are
> mostly boundaries between different parts of the UML kernel address
> space, to a new header, as-layout.h. There are also a few things here
> which aren't really related to ad
On Thu, 22 Mar 2007 23:28:41 -0700 (PDT) Christoph Lameter <[EMAIL PROTECTED]>
wrote:
> 1. Proven code from the IA64 arch.
>
> The method used here has been fine tuned for years and
> is NUMA aware. It is based on the knowledge that accesses
> to page table pages are sparse in
On Fri, 2007-03-23 at 15:12 +0900, Paul Mundt wrote:
> On Fri, Mar 23, 2007 at 02:04:30PM +0800, Wu, Bryan wrote:
> > This is the latest blackfin update patch. Because there are lots of
> > issue fixing in this one, I put all modification in one update patch
> > which is located in:
> > https://bla
i386: Convert to quicklists
Implement the i386 management of pgd and pmds using quicklists.
The i386 management of page table pages currently uses page sized slabs.
Getting rid of that using quicklists allows full use of the page flags
and the page->lru. So get rid of the improvised linked lists
Conver x86_64 to using quicklists
This adds caching of pgds and puds, pmds, pte. That way we can
avoid costly zeroing and initialization of special mappings in the
pgd.
A second quicklist is used to separate out PGD handling. Thus we can carry
the initialized pgds of terminating processes over to
From: David Miller <[EMAIL PROTECTED]>
[QUICKLIST]: Add sparc64 quicklist support.
I ported this to sparc64 as per the patch below, tested on
UP SunBlade1500 and 24 cpu Niagara T1000.
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
Index: linux-2.6.21-rc4-mm1/arch/sparc64/Kconfig
===
Quicklists for page table pages V4
V3->V4
- Rename quicklist_check to quicklist_trim and allow parameters
to specify how to clean quicklists.
- Remove dead code
V2->V3
- Fix Kconfig issues by setting CONFIG_QUICKLIST explicitly
and default to one quicklist if NR_QUICK is not set.
- Fix i386 s
Quicklist for IA64
IA64 is the origin of the quicklist implementation. So cut out the pieces
that are now in core code and modify the functions called.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
Index: linux-2.6.21-rc4-mm1/arch/ia64/mm/init.c
===
This one should hopefully fix Andy's bug.
To be queued on top of what's already in -mm please. Will make v.33 with these
changes for other trees soon.
---
The wrong bit could be unset on requeue_task which could cause an oops.
Fix that.
sched_yield semantics became almost a noop so change back t
On Fri, Mar 23, 2007 at 02:04:30PM +0800, Wu, Bryan wrote:
> This is the latest blackfin update patch. Because there are lots of
> issue fixing in this one, I put all modification in one update patch
> which is located in:
> https://blackfin.uclinux.org/gf/download/frsrelease/39/2707/blackfin-arch-
On Friday 23 March 2007 05:17, Andy Whitcroft wrote:
> Ok, I have yet a third x86_64 machine is is blowing up with the latest
> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with
> 2.6.21-rc4-mm1+hotfixes-RSDL. I have results on various hotfix levels
> so I have just fired off a set of tests acros
On Fri, 2007-03-23 at 16:59 +1100, Con Kolivas wrote:
> The deadline mechanism is easy to hit and works. Try printk'ing it.
Hm. I did (.30), and it didn't in an hours time doing this and that.
After I did the take your quota with you, it did kick in. Lots.
-Mike
-
To unsubscribe from
On Mar 22 2007 21:48, Greg KH wrote:
>On Fri, Mar 23, 2007 at 02:24:46AM +0100, Jan Engelhardt wrote:
>> On Mar 22 2007 08:28, Greg KH wrote:
>>
>> Question regarding sysfs files: How would you do something like
>> /proc/net/nf_conntrack with sysfs? Have directories named like ,
>> 0001, 00
Hi folks:
This is the latest blackfin update patch. Because there are lots of
issue fixing in this one, I put all modification in one update patch
which is located in:
https://blackfin.uclinux.org/gf/download/frsrelease/39/2707/blackfin-arch-2.6.21-rc4-mm1-update.patch
Changlogs:
1) fixed most o
Jan-Bernd Themann wrote:
The patch fixes bugs related to the probe / remove adapter
functionality (handling of OFDT nodes)
Signed-off-by: Jan-Bernd Themann <[EMAIL PROTECTED]>
applied 1-2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [E
Eric W. Biederman wrote:
Dave Hansen <[EMAIL PROTECTED]> writes:
So, I think we have a difference of opinion. I think it's _all_ about
memory pressure, and you think it is _not_ about accounting for memory
pressure. :) Perhaps we mean different things, but we appear to
disagree greatly on th
On Friday 23 March 2007 15:39, Mike Galbraith wrote:
> On Fri, 2007-03-23 at 09:50 +1100, Con Kolivas wrote:
> > Now to figure out some meaningful cheap way of improving this accounting.
>
> The accounting is easy iff tick resolution is good enough, the deadline
> mechanism is harder. I did the "q
[EMAIL PROTECTED] wrote:
From: Divy Le Ray <[EMAIL PROTECTED]>
Use tabs instead of white spaces for CHELSIO_T3 entry.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
applied
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED
[EMAIL PROTECTED] wrote:
From: Divy Le Ray <[EMAIL PROTECTED]>
Limit ethtool -g/-G to the given port's queues.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
applied 1-4
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
M
Dale Farnsworth wrote:
From: Dale Farnsworth <[EMAIL PROTECTED]>
mv643xx_eth_shutdown is needed for kexec.
Signed-off-by: Dale Farnsworth <[EMAIL PROTECTED]>
---
drivers/net/mv643xx_eth.c | 14 ++
1 file changed, 14 insertions(+)
applied
-
To unsubscribe from this list: send
Hi folks,
Changlogs:
a) Fixed issues according to Jean's review.
b) Add MAINTAINS infomation
c) add I2C_HW_B_BLACKFIN to i2c-id.h
[PATCH] Blackfin: on-chip Two Wire Interface I2C driver
The i2c linux driver for blackfin architecture which supports blackfin
on-chip TWI controller i2c operation.
On Fri, Mar 23, 2007 at 02:24:46AM +0100, Jan Engelhardt wrote:
>
> On Mar 22 2007 08:28, Greg KH wrote:
> >>
> >> > [EMAIL PROTECTED]:/home/maxim# cat
> >> > /sys/devices/system/clockevents/clockevents0/registered
> >> > lapicF:0007 M:3(periodic) C: 1
> >> > hpet
Thomas Gleixner wrote:
> On Thu, 2007-03-22 at 15:16 +0100, Adrian Bunk wrote:
Does it work if you do _not_ revert the commits, and instead replace in
drivers/acpi/processor_idle.c the
#ifdef ARCH_APICTIMER_STOPS_ON_C3
with an
#if 0
?
>>> Then NOAPIC probably works
On Thu, Mar 22, 2007 at 02:27:25PM +0100, Michal Piotrowski wrote:
> Michal Piotrowski napisał(a):
> > On 22/03/07, Ingo Molnar <[EMAIL PROTECTED]> wrote:
> >>
> >> * Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> >>
> >> > Hi Ingo,
> >>
> >> > 2.6.21-rc4-rt0
> >>
> >> > BUG: at kernel/fork.c:1033
On Thu, 22 Mar 2007 21:56:03 -0700
"Tony Luck" <[EMAIL PROTECTED]> wrote:
> On 3/22/07, KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
> > I hear some people says that "When I set stack-size-limit to 32M,
> > I want to use 32M of memory stack..." and register-stack expansion can
> > fail because sta
Andrew wrote:
> It isn't very nice. It probably won't crash, but it _can_ crash and when
I guess I got lucky, Cliff, when I snuck in the recursion in the
other cpuset.c routines that you were using as an example here ;).
Since the current kernel/cpuset.c recursion seems only to be in code
paths
On 3/22/07, KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
I hear some people says that "When I set stack-size-limit to 32M,
I want to use 32M of memory stack..." and register-stack expansion can
fail because stack is used up by memory-stack.
An interesting dilemma. If you apply this patch thoug
On Fri, 2007-03-23 at 07:08 +0530, Jan Engelhardt wrote:
>
> On Mar 22 2007 16:18, Stephane Eranian wrote:
> >
> I'd say "feature", glibc's malloc also returns an address on
> malloc(0).
>
This is implementation defined-the standard allows for return of either
null or an address.
>
> Jan
> --
>
On Fri, 2007-03-23 at 09:50 +1100, Con Kolivas wrote:
> Now to figure out some meaningful cheap way of improving this accounting.
The accounting is easy iff tick resolution is good enough, the deadline
mechanism is harder. I did the "quota follows task" thing, but nothing
good happens. That jus
On Thu, 2007-03-22 at 15:08 -0700, Greg KH wrote:
> On Fri, Mar 23, 2007 at 09:02:16AM +1100, Benjamin Herrenschmidt wrote:
> > > > i.e. First the simple bug fixes that should purely be restructure of
> > > > msi.c with no affect on anything outside of it.
> > > >
> > > > And then get into the ar
Now, ia64's hard-stack-size (rlimit.max) is sum of register-stack size and
memory-stack size. But soft-stack-size (rlimit.cur) accounitng is not sum..
they are accounted independently. This is inconsistent.
I hear some people says that "When I set stack-size-limit to 32M,
I want to use 32M of memo
ia64 expects following vm layout
==
[register-stack]
[memory-stack]
==
But, when ulimit -s is used and stack-base-address-randomization works,
vm layout is sometimes following.
==
[memory-stack]
[register-stack]
==
If this happens, register-stack cannot be expanded.
This patch fixes this bug by
Michael Ellerman <[EMAIL PROTECTED]> writes:
> On Thu, 2007-03-22 at 08:23 -0600, Eric W. Biederman wrote:
>> Michael Ellerman <[EMAIL PROTECTED]> writes:
>>
>> > Currently we never clear the msi_desc pointer in the irq_desc. This
>> > leaves us with a pointer to free'ed memory hanging around. No
Nick Piggin wrote:
> Bruce Dubbs wrote:
>> When testing an installation with tests from the Linux Test Project, my
>> kernels fail one instance of the mincore01 tests:
>>
>> mincoremincore011 PASS : expected failure: errno = 22 (Invalid
>> argument)
>> mincore012 PASS : expected failu
On 23/03/07, Tim Chen <[EMAIL PROTECTED]> wrote:
Con,
I've tried running Volanomark and found a 80% regression
with RSDL 0.31 scheduler on 2.6.21-rc4 on a 2 socket Core 2 quad cpu
system (4 cpus per socket, 8 cpus for system).
The results are sensitive to rr_interval. Using Con's patch to incre
Al Boldi wrote:
Nick Piggin wrote:
Timeslices get scaled by /proc/sys/kernel/base_timeslice. If you have bad
interactivity you could try lowering this and see if it helps.
As I am on 2.6.20, I can't really test this patch, but I tried your sched
from PlugSched and its not bad.
OK, the on
> When all write permission bits are removed from a file on
> the Windows share (e.g. using chmod ugo-w filename), the
> read-only bit is set in the file (as seen in the Windows Explorer).
> Now it is not possible to get the write permissions back (e.g. using
chmod ugo+w filename). The read-only
On Thu, Mar 22, 2007 at 01:21:46PM -0800, Tim Chen wrote:
> I've tried running Volanomark and found a 80% regression
> with RSDL 0.31 scheduler on 2.6.21-rc4 on a 2 socket Core 2 quad cpu
> system (4 cpus per socket, 8 cpus for system).
> The results are sensitive to rr_interval. Using Con's patch
On Thu, Mar 22, 2007 at 06:40:41PM -0700, Linus Torvalds wrote:
>
> [ Ok, I think it's those timers again...
>
> Ingo: let me just state how *happy* I am that I told you off when you
> wanted to merge the hires timers and NO_HZ before 2.6.20 because they
> were "stable". You were wrong, a
Dave Jones wrote:
> He wants to do this with interrupts off. on_each_cpu won't work in
> that situation.
>
I was thinking just before his big pause. But it sounds like its fairly
marginal.
> > Or patch the softlockup watchdog to add a way to temporarily disable it.
>
> Seems pretty much the
[ Ok, I think it's those timers again...
Ingo: let me just state how *happy* I am that I told you off when you
wanted to merge the hires timers and NO_HZ before 2.6.20 because they
were "stable". You were wrong, and 2.6.20 is at least in reasonable
shape. Now we just need to make sure
On Mar 22 2007 16:18, Stephane Eranian wrote:
>
>Hello,
>
>I ran into an issue with perfmon where I ended up calling
>kmalloc() with a size of zero. To my surprise, this did
>not return NULL but a valid data address.
>
>I am wondering if this is a property of kmalloc() or simply
>a bug. It is the
Please always do reply-to-all.
On Fri, 23 Mar 2007 00:27:09 +0100 "J.A. Magallón" <[EMAIL PROTECTED]> wrote:
> On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> >
> > Temporarily at
> >
> > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> >
> > Will appear l
On Wed, Mar 21, 2007 at 01:39:38PM -0700, Andrew Morton wrote:
> On Wed, 21 Mar 2007 12:41:03 -0700
> [EMAIL PROTECTED] wrote:
>
> > This was discussed on containers and we thought it would be useful
> > to reserve this flag.
> > ---
> >
> > From: Sukadev Bhattiprolu <[EMAIL PROTECTED]>
> > Subje
On Mar 22 2007 14:42, Eric Dumazet wrote:
>Instead of using :
>
>static struct loop_device *loop_dev;
>loop_dev = kmalloc(max_loop * sizeof(struct loop_device));
>
>Switch to :
>
>static struct loop_device **loop_dev;
>loop_dev = kmalloc(max_loop * sizeof(void *));
>if (!loop_dev) rollback...
>for
On Mar 22 2007 08:28, Greg KH wrote:
>>
>> > [EMAIL PROTECTED]:/home/maxim# cat
>> > /sys/devices/system/clockevents/clockevents0/registered
>> > lapicF:0007 M:3(periodic) C: 1
>> > hpet F:0003 M:1(shutdown) C: 0
>> > lapicF:0007 M:3(periodic) C: 0
On Thu, 22 Mar 2007, Siddha, Suresh B wrote:
> > You should check num_possible_nodes(), or nr_node_ids (this one is cheaper,
> > its a variable instead of a function call)
>
> But that is based on compile time option, isn't it? Perhaps I need
> to use some other mechanism to find out the platfor
On Thu, Mar 22, 2007 at 03:46:54PM -0700, Jeremy Fitzhardinge wrote:
> Cestonaro, Thilo (external) wrote:
> > It's a condition of a customer of us, so I can't change it.
> >
> > But it happens not often that my part is used. So I thought there is a
> > mechanism to disable or reset the watchd
On Thu, 2007-03-22 at 14:30 -0700, Andrew Morton wrote:
> Which tree are you patching??
We crossed in the mail: you turfed out the paravirt.h cleanup patch it
applied to.
We have rolled the fixes one patch, and am testing...
Rusty.
-
To unsubscribe from this list: send the line "unsubscribe li
If this mddev and queue got reused for another array that doesn't
register a congested_fn, this function would get called incorretly.
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./drivers/md/md.c|1 +
./drivers/md/raid5.c |3 ++-
2 files changed, 3 insertions(+
... still not sure why we need this
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./drivers/md/md.c| 41 +++--
./drivers/md/raid5.c | 12 ++--
2 files changed, 41 insertions(+), 12 deletions(-)
diff .prev/drivers/md/m
A minor new feature and 2 bug fixes for md suitable for 2.6.21
The minor feature is to make reshape (adding a drive to an array and
restriping it) work for raid4. The code is all ready, it just wasn't
used.
Thanks,
NeilBrown
[PATCH 001 of 3] md: Allow raid4 arrays to be reshaped.
[PATCH 002
All that is missing the the function pointers in raid4_pers.
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./drivers/md/raid5.c |4
1 file changed, 4 insertions(+)
diff .prev/drivers/md/raid5.c ./drivers/md/raid5.c
--- .prev/drivers/md/raid5.c2007-03-23 11:13:
On Thu, 2007-03-22 at 08:21 -0700, Linus Torvalds wrote:
>
> On Thu, 22 Mar 2007, Nick Piggin wrote:
> >
> > Nothing sleeps on PageUptodate, so I don't think that could explain it.
>
> Good point. I forget that we just test "uptodate", but then always sleep
> on "locked".
>
> > The fs: fix __b
On Thu, 22 Mar 2007 17:51:11 -0700 "Ken Chen" <[EMAIL PROTECTED]> wrote:
> +#ifdef CONFIG_HIGHMEM
> +#define pipe_kmapkmap
> +#define pipe_kmap_atomic kmap_atomic
> +#else/* CONFIG_HIGHMEM */
> +static inline void *pipe_kmap(struct page *page)
> +{
> + return (void *) p
Bruce Dubbs wrote:
When testing an installation with tests from the Linux Test Project, my
kernels fail one instance of the mincore01 tests:
mincoremincore011 PASS : expected failure: errno = 22 (Invalid
argument)
mincore012 PASS : expected failure: errno = 14 (Bad address)
mincore
It is really sad that we always call kmap and friends for every pipe
buffer page on 64-bit arch that doesn't use HIGHMEM, or on
configuration that doesn't turn on HIGHMEM.
The effect of calling kmap* is visible in the execution profile when
pipe code is being stressed. It is especially true on a
On Tue, Mar 20, 2007 at 03:19:16PM -0600, Eric W. Biederman wrote:
> Dave Hansen <[EMAIL PROTECTED]> writes:
>
> >
> > So, I think we have a difference of opinion. I think it's _all_
> > about memory pressure, and you think it is _not_ about accounting
> > for memory pressure. :) Perhaps we mean d
From: Bruce Fields <[EMAIL PROTECTED]>
The reused clientid here is a more of a problem for the client than the
server, and the client can report the problem itself if it's serious.
Signed-off-by: "J. Bruce Fields" <[EMAIL PROTECTED]>
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat ou
->readdir passes lofft_t offsets (used as nfs cookies) to
nfs3svc_encode_entry{,_plus}, but when they pass it on to
encode_entry it becomes an 'off_t', which isn't good.
So filesystems that returned 64bit offsets would lose.
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./
From: "J. Bruce Fields" <[EMAIL PROTECTED]>
This cancel_delayed_work call is called from a function that is only
called from a piece of code that immediate follows a cancel and
destruction of the workqueue, so it's clearly a mistake.
Cc: Oleg Nesterov <[EMAIL PROTECTED]>
Signed-off-by: "J. Bruce
From: Bruce Fields <[EMAIL PROTECTED]>
A regression introduced in the last set of acl patches removed the
INHERIT_ONLY flag from aces derived from the posix acl. Fix.
Signed-off-by: "J. Bruce Fields" <[EMAIL PROTECTED]>
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./fs/nf
Following are 4 small bugfixes for nfsd that are suitable for 2.6.21.
Thanks,
NeilBrown
[PATCH 001 of 4] knfsd: Allow nfsd READDIR to return 64bit cookies
[PATCH 002 of 4] knfsd: nfsd4: fix inheritance flags on v4 ace derived from
posix default ace
[PATCH 003 of 4] knfsd: nfsd4: demote "clien
On Thu, 2007-03-22 at 23:45 +, Daniel J Blueman wrote:
> Hi Shao-hua,
>
> Is the tool you mentioned last June [1] available for splitting up the
> old firmware files to the new format (eg
> /lib/firmware/intel-ucode/06-0d-06), or are updates available from
> Intel (or otherwise) in this new fo
On Thursday March 22, [EMAIL PROTECTED] wrote:
>
> Not a cfq failure, but I have been able to reproduce a different oops
> at array stop time while i/o's were pending. I have not dug into it
> enough to suggest a patch, but I wonder if it is somehow related to
> the cfq failure since it involves
Summary of what I've managed to rule out so far:
1. this problem does not occur without dm-crypt
2. this problem does not occur when the file system hasn't been moved from
the SATA disk to USB
3. Both reiserfs and ext3 are affected by this problem, but ext3
merely slows down.
4. Unmounting and r
On 3/22/07, Dan Williams <[EMAIL PROTECTED]> wrote:
On 3/22/07, Neil Brown <[EMAIL PROTECTED]> wrote:
> On Thursday March 22, [EMAIL PROTECTED] wrote:
> > On Thu, Mar 22 2007, [EMAIL PROTECTED] wrote:
> > > > 3 (I think) seperate instances of this, each involving raid5. Is your
> > > > array degr
On 3/22/07, Neil Brown <[EMAIL PROTECTED]> wrote:
On Thursday March 22, [EMAIL PROTECTED] wrote:
> On Thu, Mar 22 2007, [EMAIL PROTECTED] wrote:
> > > 3 (I think) seperate instances of this, each involving raid5. Is your
> > > array degraded or fully operational?
> >
> > Ding! A drive fell out th
Hello,
I ran into an issue with perfmon where I ended up calling
kmalloc() with a size of zero. To my surprise, this did
not return NULL but a valid data address.
I am wondering if this is a property of kmalloc() or simply
a bug. It is the case that the __kmalloc() code does not
check for zero si
Jeremy Fitzhardinge wrote:
> The softlockup watchdog is currently a nuisance in a virtual machine,
> since the whole system could have the CPU stolen from it for a long
> period of time. While it would be unlikely for a guest domain to be
> denied timer interrupts for over 10s, it could happen and
Zachary Amsden wrote:
> No, it is not unlikely. 4-way SMP VMs idling exhibit this behavior
> with NO_HZ or NO_IDLE_HZ because they get quiet enough to schedule
> nothing on the APs.
>
> And that can happen on native hardware as well.
That's a separate problem.
>>
>> Also, softlockup.c's use of j
1 - 100 of 373 matches
Mail list logo