On Wednesday 31 October 2007 11:19:54 Greg KH wrote:
> On Wed, Oct 31, 2007 at 10:25:43PM -0700, Steven King wrote:
> > My TI eZ430 (MSP-FET430UIF JTAG Tool) usb dongle works fine with
> > 2.6.23.1 and earlier, but doesn't work with 2.6.24-rc1; the
> > ti_usb_3410_5052 module is loaded but the
> You are managing it in the task struct. No need to. libnuma can handle it.
No - as noted, not all mempolicy system calls go via libnuma.
> No current version of libcpuset is available.
Wrong. It has not received wide publication yet, but it has been
provided to various others under LGPL
Noticed on PowerPC allmod config build:
drivers/scsi/aacraid/commsup.c:1342: warning: large integer implicitly
truncated to unsigned type
drivers/scsi/aacraid/commsup.c:1343: warning: large integer implicitly
truncated to unsigned type
drivers/scsi/aacraid/commsup.c:1344: warning: large integer
On Wed, Oct 31, 2007 at 10:25:43PM -0700, Steven King wrote:
> My TI eZ430 (MSP-FET430UIF JTAG Tool) usb dongle works fine with 2.6.23.1
> and earlier, but doesn't work with 2.6.24-rc1; the ti_usb_3410_5052 module is
> loaded but the device descriptor is bogus, reporting only a single
>
On Wed, Oct 31, 2007 at 05:00:59PM +0100, Peter Zijlstra wrote:
> Hi,
Hi Peter,
> Commit: b9dca1e0fcb696716840a3bc8f20a6941b484dbf
>
> seems to me that by calling enqueue_fair_task() from task_new_fair() is
> wrong. The wakeup=1 in enqueue_fair_task() will cause all non-top
s/non-top/non-task?
actuually iwl3945-rs does more than performance, it will force some
rules that could be causing this assert like transferring rate
restriction on broadcast and management frame, The could new this is
SYSASSERT which we can trace and find what causing it.
Mohamed
Zhu Yi wrote:
On Thu,
From: Christoph Lameter <[EMAIL PROTECTED]>
Date: Wed, 31 Oct 2007 21:16:59 -0700 (PDT)
> /*
> * Maximum allowed per cpu data per cpu
> */
> +#ifdef CONFIG_NUMA
> +#define PER_CPU_ALLOC_SIZE (32768 + MAX_NUMNODES * 512)
> +#else
> #define PER_CPU_ALLOC_SIZE 32768
> +#endif
> +
Christoph,
From: Christoph Lameter <[EMAIL PROTECTED]>
Date: Wed, 31 Oct 2007 18:21:02 -0700 (PDT)
> On Wed, 31 Oct 2007, David Miller wrote:
>
> > From: Christoph Lameter <[EMAIL PROTECTED]>
> > Date: Wed, 31 Oct 2007 18:12:11 -0700 (PDT)
> >
> > > On Wed, 31 Oct 2007, David Miller wrote:
> > >
> > > >
On Wed, 31 Oct 2007, Paul Jackson wrote:
> Christoph, replying to pj:
> > > Well, the mpol_nodemask_mode already is char. So I guess you're
> > > asking if we should change 'policy' to type char as well.
> >
> > Right.
>
> Ok - but why?
>
> I don't see that it matters whether policy is short
On Wed, Oct 31, 2007 at 09:08:03PM -0700, Jeremy Fitzhardinge wrote:
> Sam Ravnborg wrote:
> > It has been requested that we should let x86 behave like
> > other architectures so we at config time decide for 32 or 64 bit.
> > The challenge here is to mere the Kconfig files and I have done
> > an
On Wed, Oct 31, 2007 at 06:39:00PM -0700, Randy Dunlap wrote:
> Hi Sam,
>
> I have daily/nightly builds + test runs that use something like:
> (but more complicated than this)
>
> cp saved.config.file arch/$ARCH/config.default
> EXPORT KBUILD_DEFCONFIG=config.default
> make defconfig
On Thursday 01 November 2007 12:56, bc Wong (chimwong) wrote:
> Hi,
>
> With 2.6.16 x86_64 on a 4 core machine, I noticed
> that the filp usage (according to /proc/slabinfo)
> shoots up and keeps on increasing sharply when one
> of the CPUs is (1) locked up, or (2) very busy
> doing a lot of
I'm about to send a patch that removes the EXPERIMENTAL option and all
dependencies on EXPERIMENTAL because they are pointless.
Complete rationale:
- Many people and all distributions are currently forced to enable
CONFIG_EXPERIMENTAL since the options for many device drivers depend
on
Hi,
The patch I posted has not got any response.
Do you think ioremap and vmap information in /proc/meminfo is not useful?
or are you just busy?
Hi,
For long time I've been thought the following equation is correct:
The "MemUsage" is about "Active + Inactive + Slab + PageTables +
On Thursday 01 November 2007 12:49, Stefan Richter wrote:
> fw_device.node_id and fw_device.generation are accessed without mutexes.
> We have to ensure that all readers will get to see node_id updates
> before generation updates.
>
Hi, a few points:
- can change it to use spinlocks instead?
Using the git sources described as v2.6.24-rc1-659-gb44af9d on x86_64
architecture, I get the
following build warnings:
scripts/kconfig/qconf arch/x86/Kconfig.x86_64
drivers/net/Kconfig:1887:warning: 'select' used by config symbol 'FEC_MPC52xx'
refers to undefined
symbol 'PPC_BESTCOMM'
Hi Dave,
> > > Maybe we can use this instead:
> > > > snprintf(conn->dev.bus_id, BUS_ID_SIZE,
> > > > - "%s%2.2X%2.2X%2.2X%2.2X%2.2X%2.2X",
> > > > + "%s%s%2.2X%2.2X%2.2X%2.2X%2.2X%2.2X",
> > > > + hdev->name + 3,
> > > >
Glauber de Oliveira Costa wrote:
> under paravirt, read cr2 cannot be issued directly anymore.
> So wrap it in a macro, defined to the operation itself in case
> paravirt is off, but to something else if we have paravirt
> in the game
>
Is this actually needed? It's only used in the early
From: Stephen Hemminger <[EMAIL PROTECTED]>
Date: Wed, 31 Oct 2007 18:23:37 -0700
> The code in AF_PACKET should fix the skb before passing to user
> space so that there is no difference between accel and non-accel
> hardware. Internal choices shouldn't leak to user space. Ditto,
> the receive
Glauber de Oliveira Costa wrote:
> This patch introduces, and patch callers when needed, native
> versions for read/write_crX functions, clts and wbinvd.
>
> Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
> Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
> Acked-by: Jeremy
Christoph, replying to pj:
> > Well, the mpol_nodemask_mode already is char. So I guess you're
> > asking if we should change 'policy' to type char as well.
>
> Right.
Ok - but why?
I don't see that it matters whether policy is short or char.
> > > Could we shorten the mpol_nodemask_mode to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[kernel/signal.c:check_kill_permission() could probably benefit from
getting more consistently indented!]
I'm not sure I can grok your comment. Did you mean:
/* as per, check_kill_permission(), permit if tasks have same uid */
As to content:
This patch makes the /proc/|self/exe symlink writeable. This
functionality could be useful to potential checkpoint/restart implementations
restarting Java VMs, for example. Java uses this symlink to locate
JAVAHOME so any restarted Java program requires that /proc/self/exe points to
the jvm and
The kernel implements readlink of /proc/pid/exe by getting the file from the
first executable VMA. Then the path to the file is reconstructed and reported as
the result. While this method is often correct it does not always identify the
correct path.
I've described the problem in much greater
The kernel implements readlink of /proc/pid/exe by getting the file from the
first executable VMA. Then the path to the file is reconstructed and reported as
the result. While this method is often correct it does not always identify the
correct path.
Some applications may play games with the
The new and relatively unused (compared to VM ops) mm_struct exe file reference
uses the mmap semaphore. It may be preferrable to avoid using the mmap
semaphore at some point in the future. This patch demonstrates one way to avoid
using the mmap semaphore for the exe file reference inside
Glauber de Oliveira Costa wrote:
> This patch makes vsmp a paravirt client. It now uses the whole
> infrastructure provided by pvops. When we detect we're running
> a vsmp box, we change the irq-related paravirt operations (and so,
> it have to happen quite early), and the patching function
>
>
H... Got this to run on an ia64 big iron. One problem is the sizing of
the pool. Somehow this needs to be dynamic.
Apply this fix on top of the others.
---
include/asm-ia64/page.h |2 +-
include/asm-ia64/percpu.h |9 ++---
mm/allocpercpu.c | 12 ++--
3
Hi!
I compiled kernel 2.6.24-rc1 (latest git as of today) on a Box with 256MB Ram.
During "make modules_install" I got these errors:
DEPMOD 2.6.24-rc1-default
WARNING: Can't read
module /lib/modules/2.6.24-rc1-default/kernel/net/bridge/bridge.ko: Cannot
allocate memory
WARNING: Can't read
On Thu, Nov 01, 2007 at 08:58:55AM +0530, Kamalesh Babulal wrote:
> Shaw Vrana wrote:
> > Yeah, I get the same with 2.6.24-rc1.
> >
> >
> > On Tue, Oct 23, 2007 at 05:48:54PM +0200, Thomas Meyer wrote:
> >> Thomas Meyer schrieb:
> >>> Oct 23 17:13:55 [kernel] usb 1-1: new high speed USB device
Sam Ravnborg wrote:
> It has been requested that we should let x86 behave like
> other architectures so we at config time decide for 32 or 64 bit.
> The challenge here is to mere the Kconfig files and I have done
> an attempt to do so.
>
> +source "mm/Kconfig"
>
> -config X86_VISWS_APIC
>
On Wed, 24 Oct 2007 20:11:07 +0200 Ingo Molnar wrote:
>
> * Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> > * Ingo Molnar <[EMAIL PROTECTED]> wrote:
> >
> > > i have triggered this and fixed it the right way - see the patch
> > > below. This fixes the 2.6.24-rc1 build error.
> >
> > and this
Shaw Vrana wrote:
> Yeah, I get the same with 2.6.24-rc1.
>
>
> On Tue, Oct 23, 2007 at 05:48:54PM +0200, Thomas Meyer wrote:
>> Thomas Meyer schrieb:
>>> Oct 23 17:13:55 [kernel] usb 1-1: new high speed USB device using
>>> ehci_hcd and address 7
>>> Oct 23 17:13:55 [kernel] usb 1-1:
On 11/1/07, Casey Schaufler <[EMAIL PROTECTED]> wrote:
>
> --- Peter Dolding <[EMAIL PROTECTED]> wrote:
>
>
> > Improvements to the single security framework are getting over looked.
>
> Please post proposed patches.
>
> > I would have personally though selinux would have done Posix file
> >
* Roland McGrath ([EMAIL PROTECTED]) wrote:
>
> This adds some new magic in the MODPOST phase for CONFIG_MARKERS.
> Analogous to the Module.symvers file, the build will now write a
> Module.markers file when CONFIG_MARKERS=y is set. This file lists
> the name, defining module, and format string
On Wed, Oct 31, 2007 at 04:08:21PM -0700, Linus Torvalds wrote:
>
>
> On Wed, 31 Oct 2007, Nick Piggin wrote:
> >
> > No that would be great. Fingers crossed it won't cause any problems.
>
> I actually doubt it will cause problems.
>
> We made much bigger changes to ptrace support when we
> -Original Message-
> From: Anton Vorontsov [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 01, 2007 5:59 AM
> To: Li Yang-r58472
> Cc: [EMAIL PROTECTED]; linux-kernel@vger.kernel.org;
> [EMAIL PROTECTED]
> Subject: Re: [PATCH] ucc_geth: add support for netpoll
>
> On Mon, Oct 29,
--- Peter Dolding <[EMAIL PROTECTED]> wrote:
> Improvements to the single security framework are getting over looked.
Please post proposed patches.
> I would have personally though selinux would have done Posix file
> capabilities as a general service to all.
Posix capabilities predate
On 11/1/07, Dave Young <[EMAIL PROTECTED]> wrote:
> On 10/31/07, Marcel Holtmann <[EMAIL PROTECTED]> wrote:
> > Hi Dave,
> >
> > > > > > diff -upr linux/net/bluetooth/hci_sysfs.c
> > > > > > linux.new/net/bluetooth/hci_sysfs.c
> > > > > > --- linux/net/bluetooth/hci_sysfs.c 2007-10-31
The Clear and Important thing is there is already a single security framework.
The single security framework is the security that exists when no LSM
is loaded. It turns out the more I look most of my model already
exists just not being used effectively. There is a capabilities frame
work at
Hi,
With 2.6.16 x86_64 on a 4 core machine, I noticed
that the filp usage (according to /proc/slabinfo)
shoots up and keeps on increasing sharply when one
of the CPUs is (1) locked up, or (2) very busy
doing a lot of printk()'s with KERN_EMERG.
In the case of (1), it's permanent until it runs
read_rom() obtained a fresh new fw_device.generation for each read
transaction (unless the compiler performed very aggressive inlining in
read_bus_info_block). It's unlikely but not impossible that we could
end up with a corrupt fetched ROM image if there was a generation change
during the ROM
Stephen Hemminger wrote:
On Wed, 31 Oct 2007 14:43:51 -0400
Dave Johnson <[EMAIL PROTECTED]> wrote:
Depending on the network driver, I'm seeing different behavior if
a .1q packet is received to an PF_PACKET, SOCK_RAW, ETH_P_ALL socket.
On devices what do not use NETIF_F_HW_VLAN_RX, the
Two fixes:
- There was a small window where a login or reconnect job could use an
already updated card generation with an outdated node ID. We better
use the fw_device.generation here, not the fw_card.generation.
- Insert a memory barrier to ensure that the device generation is read
fw_device.node_id and fw_device.generation are accessed without mutexes.
We have to ensure that all readers will get to see node_id updates
before generation updates.
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
---
drivers/firewire/fw-device.c |6 ++
On Thu, 2007-11-01 at 01:12 +0100, Pavel Machek wrote:
> iwl3945: Microcode SW error detected. Restarting 0x8208.
> iwl3945: Start IWL Error Log Dump:
> iwl3945: Status: 0x00010172, Config: count: 1
> iwl3945: Desc Time asrtPC blink2 ilink1 nmiPC Line
> iwl3945:
On Wednesday, 31 October 2007 01:52, Pavel Machek wrote:
>
> Hi!
>
> ...does not seem to work too well :-(. It connects with the AP
> (good!), and survives some "normal" use, but it died at first big
> tcpspray (bd!).
Is this a regression from 2.6.23?
> Oct 31 01:03:57 amd log1n[1411]:
Hi Sam,
I have daily/nightly builds + test runs that use something like:
(but more complicated than this)
cp saved.config.file arch/$ARCH/config.default
EXPORT KBUILD_DEFCONFIG=config.default
make defconfig
This stopped working in 2.6.24-rc1-git3. git2 worked as (I) expected.
Is there
Stephen Hemminger wrote:
The code in AF_PACKET should fix the skb before passing to user space
so that there is
no difference between accel and non-accel hardware. Internal choices
shouldn't
leak to user space. Ditto, the receive checksum offload should be
fixed up as well.
Ok, I guess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ackd.
Cheers
Andrew
Serge E. Hallyn wrote:
>>From 5bff8967f45a35f858b96ca673d9bf98eac53d49 Mon Sep 17 00:00:00 2001
> From: Serge E. Hallyn <[EMAIL PROTECTED]>
> Date: Wed, 31 Oct 2007 11:22:04 -0500
> Subject: [PATCH 1/1] file capabilities: allow
Ben Greear wrote:
Stephen Hemminger wrote:
On Wed, 31 Oct 2007 14:43:51 -0400
Dave Johnson <[EMAIL PROTECTED]> wrote:
Depending on the network driver, I'm seeing different behavior if
a .1q packet is received to an PF_PACKET, SOCK_RAW, ETH_P_ALL socket.
On devices what do not use
On Wed, 31 Oct 2007, David Miller wrote:
> From: Christoph Lameter <[EMAIL PROTECTED]>
> Date: Wed, 31 Oct 2007 18:12:11 -0700 (PDT)
>
> > On Wed, 31 Oct 2007, David Miller wrote:
> >
> > > All I can do now is bisect and then try to figure out what about the
> > > guilty change might cause the
From: Christoph Lameter <[EMAIL PROTECTED]>
Date: Wed, 31 Oct 2007 18:12:11 -0700 (PDT)
> On Wed, 31 Oct 2007, David Miller wrote:
>
> > All I can do now is bisect and then try to figure out what about the
> > guilty change might cause the problem.
>
> Reverting the 7th patch should avoid using
On Wed, 31 Oct 2007, David Miller wrote:
> It crashes when SSHD starts, the serial console GETTY hasn't
> started up yet so I can't even log in to run those commands
> Christoph.
Hmmm... Bad.
> All I can do now is bisect and then try to figure out what about the
> guilty change might cause the
From: Ben Greear <[EMAIL PROTECTED]>
Date: Wed, 31 Oct 2007 18:06:34 -0700
> DaveM did the HW Accel for VLANs if I remember correctly...perhaps he
> has some input?
Not really, I'm busy and also not motivated to work on this, someone
else will need to.
-
To unsubscribe from this list: send the
From: Christoph Lameter <[EMAIL PROTECTED]>
Date: Wed, 31 Oct 2007 18:01:34 -0700 (PDT)
> On Wed, 31 Oct 2007, David Miller wrote:
>
> > Without DEBUG_VM I get a loop of crashes shortly after SSHD
> > is started, I'll try to track it down.
>
> Check how much per cpu memory is in use by
>
> cat
This adds some new magic in the MODPOST phase for CONFIG_MARKERS.
Analogous to the Module.symvers file, the build will now write a
Module.markers file when CONFIG_MARKERS=y is set. This file lists
the name, defining module, and format string of each marker,
separated by \t characters. This
On 10/31/07, Marcel Holtmann <[EMAIL PROTECTED]> wrote:
> Hi Dave,
>
> > > > > diff -upr linux/net/bluetooth/hci_sysfs.c
> > > > > linux.new/net/bluetooth/hci_sysfs.c
> > > > > --- linux/net/bluetooth/hci_sysfs.c 2007-10-31 10:21:00.0
> > > > > +0800
> > > > > +++
On Wed, 31 Oct 2007, David Miller wrote:
> Without DEBUG_VM I get a loop of crashes shortly after SSHD
> is started, I'll try to track it down.
Check how much per cpu memory is in use by
cat /proc/vmstat
currently we have a 32k limit there.
-
To unsubscribe from this list: send the line
From: Christoph Lameter <[EMAIL PROTECTED]>
Date: Wed, 31 Oct 2007 17:53:23 -0700 (PDT)
> > This patch fixes build failures with DEBUG_VM disabled.
>
> Well there is more there. Last minute mods sigh. With DEBUG_VM you likely
> need this patch.
Without DEBUG_VM I get a loop of crashes shortly
> This patch fixes build failures with DEBUG_VM disabled.
Well there is more there. Last minute mods sigh. With DEBUG_VM you likely
need this patch.
---
include/linux/percpu.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux-2.6/include/linux/percpu.h
On Wed, 31 Oct 2007 15:58:33 -0700
[EMAIL PROTECTED] wrote:
> +int remove_memory(u64 start, u64 size)
> +{
> + unsigned long start_pfn, end_pfn;
> + int ret;
> +
> + start_pfn = start >> PAGE_SHIFT;
> + end_pfn = start_pfn + (size >> PAGE_SHIFT);
> + ret =
From: Christoph Lameter <[EMAIL PROTECTED]>
Date: Wed, 31 Oct 2007 17:31:12 -0700 (PDT)
> Others may have the same issue.
>
> git pull git://git.kernel.org/pub/scm/linux/kernel/git/christoph/slab.git
> allocpercpu
>
> should get you the whole thing.
This patch fixes build failures with
On Wed, 31 Oct 2007 12:27:24 +0100 (CET) Jiri Kosina <[EMAIL PROTECTED]> wrote:
>
> I already have this fixed in my tree, sorry.
As long as it gets fixed, I don't mind.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
http://www.canb.auug.org.au/~sfr/
pgpWcx0XupYc4.pgp
Hello, Jeff.
Jeff Garzik wrote:
> That's easy for the PIO case. But CD writing is normally DMA, which
> means you will get a DMA engine exception if the device wants to give
> you more data than the scatter/gather entries permit.
For sense data and mode pages, the standard-sanctioned way to
On Wed, 31 Oct 2007, David Miller wrote:
> > git pull git://git.kernel.org/pub/scm/linux/kernel/git/christoph/slab.git
> > performance
> >
> > and then you should be able to apply these patches.
>
> Thanks a lot Chrisoph.
Others may have the same issue.
git pull
From: Christoph Lameter <[EMAIL PROTECTED]>
Date: Wed, 31 Oct 2007 17:26:16 -0700 (PDT)
> Do
>
> git pull git://git.kernel.org/pub/scm/linux/kernel/git/christoph/slab.git
> performance
>
> and then you should be able to apply these patches.
Thanks a lot Chrisoph.
-
To unsubscribe from this
On Wed, 31 Oct 2007, David Miller wrote:
>
> Are these patches against -mm or mainline?
>
> I get a lot of rejects starting with patch 6 against
> mainline and I really wanted to test them out on sparc64.
Hmmm... They are against the current slab performance head (which is in mm
but it has
Are these patches against -mm or mainline?
I get a lot of rejects starting with patch 6 against
mainline and I really wanted to test them out on sparc64.
Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Hi!
> > tcpspray -n 1 -b 1000 10.0.0.2
> >
> > Oct 31 01:42:56 amd kernel: iwl3945: Microcode SW error detected.
> > Restarting 0x8208.
> > Oct 31 01:42:56 amd kernel: iwl3945: Error Reply type 0x0005 cmd
> > REPLY_TX (0x1C) seq 0x02C7 ser 0x004B
> > Oct 31 01:42:58 amd kernel:
Currently each call to alloc_percpu allocates an array of pointer to objects.
For each operation on a percpu structure we need to follow a pointer from that
map. Usually a processor used only the entry for its own processor id in that
array. The rest of the bytes in the cacheline are not needed.
Use this_cpu_ptr to optimize access to the per cpu area in the fastpaths.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
mm/slub.c | 27 +++
1 file changed, 19 insertions(+), 8 deletions(-)
Index: linux-2.6/mm/slub.c
Remove the fields in kmem_cache_cpu that were used to cache data from
kmem_cache when they were in different cachelines. The cacheline that holds
the per cpu array pointer now also holds these values. We can cut down the
kmem_cache_cpu size to almost half.
The get_freepointer() and
Using allocpercpu removes the needs for the per cpu arrays in the kmem_cache
struct.
These could get quite big if we have to support system of up to thousands of
cpus.
The use of alloc_percpu means that:
1. The size of kmem_cache for SMP configuration shrinks since we will only
need 1 pointer
Population and depopulation is no longer needed since newly created
per cpu areas will have all the fields needed. Teardown of per cpu
areas will remove objects no longer needed.
This basically reverts the API to the way it was before the population and
depopulation went in. There is only a
Support for this_cpu_ptr() is important for those arches that allow a faster
way to get to the per cpu area of the local processor.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
include/asm-generic/percpu.h |4
include/asm-ia64/percpu.h|3 +++
This patch increases the speed of the SLUB fastpath by
improving the per cpu allocator and makes it usable for SLUB.
Currently allocpercpu manages arrays of pointer to per cpu objects.
This means that is has to allocate the arrays and then populate them
as needed with objects. Although these
Disguising costs a few cycles in the hot paths. So switch it off if
we are not debuggin.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
include/linux/percpu.h |4
1 file changed, 4 insertions(+)
Index: linux-2.6/include/linux/percpu.h
On Wed, Oct 31, 2007 at 05:00:16PM -0500, Kiyoshi Ueda wrote:
> How about the case that other dm device is stacked on the dm device?
> (e.g. dm-linear over dm-multipath over i2o with bounce_pfn=64GB, and
> the multipath table is changed to i2o with bounce_pfn=1GB.)
Let's not broaden the
Hi Hugh, I've addressed all of your concerns and am happy to report that the
newly revised unionfs_writepage works even better, including under my
memory-pressure conditions. To summarize my changes since the last time:
- I'm only masking __GFP_FS, not __GFP_IO
- using find_or_create_page to
>From 5bff8967f45a35f858b96ca673d9bf98eac53d49 Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn <[EMAIL PROTECTED]>
Date: Wed, 31 Oct 2007 11:22:04 -0500
Subject: [PATCH 1/1] file capabilities: allow sigcont within session (v2)
(This is a proposed fix to
Yeah, I get the same with 2.6.24-rc1.
On Tue, Oct 23, 2007 at 05:48:54PM +0200, Thomas Meyer wrote:
> Thomas Meyer schrieb:
> > Oct 23 17:13:55 [kernel] usb 1-1: new high speed USB device using
> > ehci_hcd and address 7
> > Oct 23 17:13:55 [kernel] usb 1-1: configuration #1 chosen from 1 choice
From: Dave Jones <[EMAIL PROTECTED]>
Date: Wed, 31 Oct 2007 17:29:32 -0400
> make headers_check currently fails in mainline with..
>
> include/linux/tipc_config.h requires linux/string.h, which does not exist in
> exported headers
>
> There's no reason to even include this in this header as
On Wed, 31 Oct 2007, Nick Piggin wrote:
>
> No that would be great. Fingers crossed it won't cause any problems.
I actually doubt it will cause problems.
We made much bigger changes to ptrace support when we disallowed writing
to read-only shared memory areas (we used to do the magic
This patch contains the scheduled removal of legacy I2C RTC drivers with
replacement drivers.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
Documentation/feature-removal-schedule.txt |7
arch/powerpc/platforms/83xx/mpc832x_mds.c | 24 -
arch/powerpc/platforms/83xx/mpc834x_mds.c
With paravirualization, hypervisors needs to handle the gdt,
that was right to this point only used at very early
inialization code. Hypervisors (lguest being the current case)
are commonly modules, so make it an export
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
Signed-off-by:
This patch turns the basic descriptor handling into native_
functions. It is basically write_idt, load_idt, write_gdt,
load_gdt, set_ldt, store_tr, load_tls, and the ones
for updating a single entry.
In the process of doing that, we change the definition of
load_LDT_nolock, and caller sites have
This patch turns the set_p{te,md,ud,gd} functions into their
native_ versions. There is no need to patch any caller.
Also, it adds pte_update() and pte_update_defer() calls whenever
we modify a page table entry. This last part was coded to match
i386 as close as possible.
Pieces of the header
Two main issues fixed here are:
- An improper use of in-struct lock to protect an open count
- Use of urb status for -EINPROGRESS
Also, along the way:
- Change usb_unlink_urb to usb_kill_urb. Apparently there's no need
to use usb_unlink_urb whatsoever in this driver, and the old use of
The interrupt initialization routine becomes native_init_IRQ and will
be overriden later in case paravirt is on. The interrupt array is made visible
for guests such lguest, that will need to have their own initialization
mechanism (though using most of the same irq lines) later on.
Signed-off-by:
On Wed, Oct 31, 2007 at 08:59:41AM -0700, Linus Torvalds wrote:
>
>
> On Wed, 31 Oct 2007, Nick Piggin wrote:
> >
> > Well the patch is right, in the context of the regression I introduced
> > (and so it should probably go into 2.6.23).
>
> Yeah, it probably is fine for -stable.
>
> And if
Use the new generic cmpxchg_local (disables interrupt). Also use the generic
cmpxchg as fallback if SMP is not set.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
include/asm-m68knommu/system.h | 28 +++-
1 file
On m32r, use the new cmpxchg_local as primitive for the local_cmpxchg
operation.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
Acked-by: Hirokazu Takata <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
---
include/asm-m32r/local.h | 362 ++-
1 file
Add __xchg_local, xchg_local (define), __cmpxchg_local_u32, __cmpxchg_local,
cmpxchg_local(macro).
cmpxchg_local and cmpxchg64_local will use the architecture specific
__cmpxchg_local_u32 for 32 bits arguments, and use the generic
__cmpxchg_local_generic for 8, 16 and 64 bits arguments.
Use the new generic cmpxchg_local (disables interrupt). Also use the generic
cmpxchg as fallback if SMP is not set.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
include/asm-cris/system.h | 15 +++
1 file changed, 15
Use the new generic cmpxchg_local (disables interrupt) for 8, 16 and 64 bits
cmpxchg_local. Use the __cmpxchg_u32 primitive for 32 bits cmpxchg_local.
Note that cmpxchg only uses the __cmpxchg_u32 or __cmpxchg_u64 and will cause
a linker error if called with 8 or 16 bits argument.
Signed-off-by:
the #endif /* CONFIG_SMP */ should cover the default condition, or it may cause
bad parameter to be silently missed.
To make it work correctly, we have to remove the ifdef CONFIG SMP surrounding
__xchg_called_with_bad_pointer declaration. Thanks to Adrian Bunk for detecting
this.
Use the standard __cmpxchg for every type that can be updated atomically.
Use the new generic cmpxchg_local (disables interrupt) for other types.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
include/asm-s390/system.h |
Use the new generic cmpxchg_local (disables interrupt). Also use the generic
cmpxchg as fallback if SMP is not set.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
include/asm-arm/system.h | 15 +++
1 file changed, 15
Actually, on 386, cmpxchg and cmpxchg_local fall back on
cmpxchg_386_u8/16/32: it disables interruptions around non atomic
updates to mimic the cmpxchg behavior.
The comment:
/* Poor man's cmpxchg for 386. Unsuitable for SMP */
already present in cmpxchg_386_u32 tells much about how this cmpxchg
1 - 100 of 894 matches
Mail list logo
