Alexey Dobriyan wrote:
+asmlinkage long sys_lutimesat(int dfd, char __user *filename, struct timeval
__user *utimes)
Could we get these to take struct timespec instead of struct timeval?
Right now we have a real problem in that the interfaces that *set* times
take struct timeval
S.Çağlar Onur wrote:
g means r+i so the register allocator in the -O0 case is selecting r
while in the optimize case is selecting i
g means rmi, not ri.
-hpa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
Andreas Block wrote:
Aren't there platforms for which irq = 0 is a valid irq ?
As far as I understand the PCI spec, the answer to your question seems
to be: no
(or I'm missing something).
Don't get me wrong. I'm not talking about system IRQs, but about the
value of the Interrupt Pin
On Sat, Jan 27, 2007 at 07:28:07PM -0800, Zwane Mwaikambo wrote:
--- linux-2.6.20-rc4-mm1/include/linux/agpgart.h 27 Jan 2007 22:04:06
- 1.1.1.1
+++ linux-2.6.20-rc4-mm1/include/linux/agpgart.h 27 Jan 2007 22:41:23
-
@@ -114,6 +114,67 @@ typedef struct _agp_unbind {
Jan Engelhardt wrote:
On Jan 27 2007 10:31, Marc Perkel wrote:
[]
Sorry about that. I'm using Fedora Core 6. /dev/md0
and /dev/md1, buth of which are raid 1 arrays survive
the reboot. But when I make a raid 0 out of those two
raid arrays that's what is vanishing.
That's interesting. I am
Hi there,
Just a quick and easy question for you.
I am aware of three ways to make my laptop suspend/hibernate:
1. suspend
2. ususpend
3. suspend2
The first two are directly part of the official linux
distribution and the third one is easy to install into it.
Here is my question: what is the
DB == Dirk Behme [EMAIL PROTECTED] writes:
DB Any chance to have anything like an auto-update mbox archive of
DB LKML? Would be nice for people not permanently subscribed to LKML.
Perhaps nntp://news.gmane.org/gmane.linux.kernel can help, even if it
isn't exactly what you asked for.
/Benny
* Sunil Naidu [EMAIL PROTECTED] wrote:
There is some confusion for me while configuring a rt kernel
proceeding for experiments. I did choose the following:-
NO_HZ=y
HIGH_RES_TIMERS=y
SMP=y
PREEMPT_VOLUNTARY=y
PREEMPT_SOFTIRQS=y
PREEMPT_HARDIRQS=y
SPINLOCK_BKL=y
CLASSIC_RCU=y
When I booted last time with 2.6.20(as I remember -rc4),
I don't see this issue:
all kernel message instead of just
go to syslog-ng and then into /var/log/messages
also go to console.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Andrew Morton napsal(a):
Temporarily at
http://userweb.kernel.org/~akpm/2.6.20-rc6-mm1/
Unable to select IPV6. Menuconfig doesn't offer it when INET is selected. When
it's not it appears in the menu, but after state change it gets away. The same
behaviour in xconfig, gconfig.
$
Paweł Sikora wrote:
On Saturday 27 of January 2007 10:05:53 Avi Kivity wrote:
g appears to be equivalent to rmi, if i is impossible, gcc is free
to use r or m, no?
`r'
A register operand is allowed provided that it is in a general
register.
`g'
Any register, memory or
S.Çağlar Onur wrote:
27 Oca 2007 Cts tarihinde, Avi Kivity şunları yazmıştı:
The patch looks correct, but I don't understand the gcc error message.
Are we sure this isn't a gcc 4.2 bug?
g appears to be equivalent to rmi, if i is impossible, gcc is free
to use r or m, no?
Accorgind to
CompactFlash cards in a passive PCMCIA adapter don't seem
to like the ATA_CMD_SET_FEATURES command, which causes
libata device probing to fail.
Since PCMCIA only allows PIO mode 0 anyway, there is no
point in ever setting a higher speed. Adding the dummy
function seems to do the right thing.
From: Giuseppe Bilotta [EMAIL PROTECTED]
Some nVidia video cards have broken EDID information. Using nvidiafb
with CONFIG_FB_NVIDIA_I2C enabled on these systems causes the console
framebuffer to use wrong timing information, causing the display to be
extremely 'snowy'. Since most distribution
Andrew Morton napsal(a):
Temporarily at
http://userweb.kernel.org/~akpm/2.6.20-rc6-mm1/
Under disk load I get disk:
[ cut here ]
kernel BUG at /home/l/latest/xxx/block/cfq-iosched.c:1026!
invalid opcode: [#1]
SMP
last sysfs file:
Am Sonntag 28 Januar 2007 schrieb Giuseppe Bilotta:
From: Giuseppe Bilotta [EMAIL PROTECTED]
Solve the issue by introducing a new boolean module parameter (useedid)
which can be set to 0 to prevent the driver from using the EDID
information.
I don't know whether this is possible, but
Hi Andrew,
On 1/28/07, Andrew Morton [EMAIL PROTECTED] wrote:
This gets its local interrupt state mucked up.
BUG: sleeping function called from invalid context at mm/slab.c:3038
in_atomic():0, irqs_disabled():1
no locks held by init/1.
irq event stamp: 656902
hardirqs last enabled at
Hi,
With kernel 2.6.19 I was able to boot using the pata_via driver
I tried to compile 2.6.20-rc6 and now I get a unknown device: sda3
error when I try to boot.
I compiled 2.6.20-rc6 by copying over the .config from the 2.6.19 tree
and running a make oldconfig make
Am I doing something wrong?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am not sure if I have seen it before, possibly yes.
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth:
two of the ioctl defines in the i2o-dev.h header break when used from
userspace as they are defined in terms of u8/u32 ... trivial attached patch
fixes this to use __u8/__u32
-mike
pgpu1tChniByh.pgp
Description: PGP signature
Make sure exported I2O ioctls utilize userspace safe types.
This patch-set breaks up the global file_list_lock which was found to be a
severe contention point under basically any filesystem intensive workload.
It has been part of the -rt kernel for some time now and is deemed solid and
useful enough to post in its own right. This contention should also
this can be used to reset a held lock's subclass, for arbitrary-depth
iterated data structures such as trees or lists which have per-node
locks.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
---
include/linux/lockdep.h |4 ++
kernel/lockdep.c
From: Ingo Molnar [EMAIL PROTECTED]
filevec_add_drain_all() is called under locks and schedule_on_each_cpu() can
schedule. Solve this by using the new schedule_on_each_cpu_wq().
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
fs/file_table.c |
From: Ingo Molnar [EMAIL PROTECTED]
Provide a schedule_on_each_cpu_wq() function that uses a workqueue to do all
the work. This avoid the calling process to schedule.
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/linux/workqueue.h |
Break the protection of sb-s_files out from under the global file_list_lock.
sb-s_files is converted to a lock_list. furthermore to prevent the
lock_list_head of getting too contended with concurrent add operations
the add is buffered in per cpu filevecs.
This would ordinarily require a flush
This barrier thing is constructed so that it will not write in the sync()
condition (the hot path) when there are no active lock sections; thus avoiding
cacheline bouncing. -- I'm just not sure how this will work out in relation to
PI. We might track those in the barrier scope and boost those by
From: Ingo Molnar [EMAIL PROTECTED]
file_kill() has to look at the file's inode (for the barrier logic),
hence make sure we free the inode before the file.
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
---
fs/pipe.c | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
David Ford david at blue-labs.org writes:
Any me toos out there, any suggestions?
Big me too here. I use this board to run workstation and home samba services
and it seems that under stress, the connection gets lost. Can't put my finger on
the when/what/why too.
I get the feeling though that
the hdreg.h exports some SIZE defines to userspace but it utilizes sizeof(u8)
in its definition ... that's no good so the trivial attached patch changes
that to sizeof(__u8)
-mike
pgp3pxtX8U9TZ.pgp
Description: PGP signature
Use __u8 rather than u8 in SIZE defines exported to userspace.
On Sun, 28 Jan 2007 11:34:01 +0100
Arnd Bergmann [EMAIL PROTECTED] wrote:
CompactFlash cards in a passive PCMCIA adapter don't seem
to like the ATA_CMD_SET_FEATURES command, which causes
libata device probing to fail.
Since PCMCIA only allows PIO mode 0 anyway, there is no
point in ever
On Jan 28 2007 12:05, Michael Tokarev wrote:
Jan Engelhardt wrote:
That's interesting. I am using Aurora Corona, and all but md0 vanishes.
(Reason for that is that udev does not create the nodes md1-md31 on
boot, so mdadm cannot assemble the arrays.)
This is nonsense.
Mdadm creates those
Robert P. J. Day wrote:
Fix what looks like an obvious typo in the file drivers/kvm/svm.c.
Signed-off-by: Robert P. J. Day [EMAIL PROTECTED]
---
is this, in fact, a typo?
It is. Well spotted.
I tested this on my AMD machine, and everything still works.
Acked-by: Avi Kivity [EMAIL
On Sun, 28 Jan 2007, Jes Sorensen wrote:
Theodore Tso wrote:
Footnote FYI, the anticipated rooms costs at Cambridge will be 60-70
pounds, and this is for single rooms with private baths
With this daily taxes, you can go to a good resort in Brazil (breakfast
and maybe lunch included) if you
Ensure no new files will be added when we're inspecting 'all' files. Without
this, files could be added in front while we're iterating and we'd miss those.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
---
fs/file_table.c |9
Change the PG_nonewref operations into locking primitives and place them
so that they provide page level serialization with regard to the page_tree
operations. (basically replace the tree_lock with a per page lock).
The normal page lock has sufficiently different (and overlapping) scope and
Currently the tree_lock protects mapping-nrpages, this will not be
possible much longer. Hence abstract the access to this variable so that
it can be easily replaced by an atomic_ulong_t.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
arch/sh64/lib/dbg.c |2 +-
fs/block_dev.c
From: Nick Piggin [EMAIL PROTECTED]
If we can be sure that elevating the page_count on a pagecache
page will pin it, we can speculatively run this operation, and
subsequently check to see if we hit the right page rather than
relying on holding a lock or otherwise pinning a reference to the
page.
From: Nick Piggin [EMAIL PROTECTED]
Rather than sign direct radix-tree pointers with a special bit, sign
the indirect one that hangs off the root. This means that, given a
lookup_slot operation, the invalid result will be differentiated from
the valid (previously, valid results could have the bit
Provide support for concurrent write side operations without changing the API
for all current uses.
Concurrency is realized by means of two locking models; the simple one is
ladder locking, the more complex one is path locking.
Ladder locking is like walking down a ladder, you place your foot
Remove the tree_lock, change address_space::nrpages to atomic_ulong_t
because its not protected any longer and use the concurrent radix tree API to
protect the modifying radix tree operations.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
fs/buffer.c |6 --
fs/inode.c
implement the speculative find_get_pages_tag.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
mm/filemap.c | 42 +-
1 file changed, 33 insertions(+), 9 deletions(-)
Index: linux-2.6/mm/filemap.c
Livelock scenario pointed out by Nick.
SetPageNoNewRefs(page);
*** preempted here ***
page_cache_get_speculative() {
while (PageNoNewRefs(page)) /* livelock */
}
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
its the last read_lock user of tree_lock, and since its unused remove
it rather than convert it.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/linux/pagemap.h |2 --
mm/filemap.c| 20
2 files changed, 22 deletions(-)
Index:
with all the read_lock uses of the tree_lock gone, change it into
a spinlock.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
fs/buffer.c |4 ++--
fs/inode.c |2 +-
include/asm-arm/cacheflush.h|4 ++--
include/asm-parisc/cacheflush.h |
provide an unsigned long atomic type.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/asm-generic/atomic.h | 45 +++
1 file changed, 45 insertions(+)
Index: linux-2.6-git2/include/asm-generic/atomic.h
With Nick leading the way to getting rid of the read side of the tree_lock,
this work continues by breaking the write side of said lock.
Aside from breaking MTD this version of the concurrent page cache seems
rock solid on my dual core x86_64 box.
-
To unsubscribe from this list: send the line
Simple implementation of radix_tree_gang_lookup_tag_slot()
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/linux/radix-tree.h |5 ++
lib/radix-tree.c | 81 ++---
2 files changed, 82 insertions(+), 4 deletions(-)
Index:
From: Nick Piggin [EMAIL PROTECTED]
Introduce a gang_lookup_slot function which is used by lockless pagecache.
Signed-off-by: Nick Piggin [EMAIL PROTECTED]
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/linux/radix-tree.h |7 +++
lib/radix-tree.c | 86
From: Nick Piggin [EMAIL PROTECTED]
Combine page_cache_get_speculative with lockless radix tree lookups to
introduce lockless page cache lookups (ie. no mapping-tree_lock on
the read-side).
The only atomicity changes this introduces is that the gang pagecache
lookup functions now behave as if
Greg KH [EMAIL PROTECTED] writes:
On Fri, Jan 26, 2007 at 11:43:22AM +0100, Rainer Weikusat wrote:
Greg KH [EMAIL PROTECTED] writes:
On Thu, Jan 25, 2007 at 04:20:55PM +0100, Rainer Weikusat wrote:
2.6.19 introduced changes to the UHCI handling of interrupt URBs that
caused at least some
27-01-2007, H. Peter Anvin:
[]
Sure... it's the DL380 G2 that used to be zeus.kernel.org. It's not
ideal (in particular, I would have preferred a 64-bit machine), but it
has the advantage that it's proven itself rock-solid over the years, it
has all the hands-off management features, we
Eradicate global locks.
- kmap_lock is removed by extensive use of atomic_t, a new flush
scheme and modifying set_page_address to only allow NULL-virt
transitions.
A count of 0 is an exclusive state acting as an entry lock. This is done
using inc_not_zero and cmpxchg. The restriction on
Original-Nachricht
Datum: Sat, 27 Jan 2007 18:42:30 +0100
Von: Adrian Bunk [EMAIL PROTECTED]
An: Linus Torvalds [EMAIL PROTECTED], Andrew Morton [EMAIL PROTECTED]
Betreff: 2.6.20-rc6: known unfixed regressions (v2) (part 2)
This email lists some known regressions in 2.6.20-rc6
jbd function called instead of fs specific one.
Signed-off-by: Dmitriy Monakhov [EMAIL PROTECTED]
--
diff --git a/fs/ext3/inode.c b/fs/ext3/inode.c
index beaf25f..8a824f4 100644
--- a/fs/ext3/inode.c
+++ b/fs/ext3/inode.c
@@ -947,7 +947,7 @@ out:
static int ext3_get_block(struct inode
On Sun, Jan 28, 2007 at 12:51:21PM +0100, Peter Zijlstra wrote:
This barrier thing is constructed so that it will not write in the sync()
condition (the hot path) when there are no active lock sections; thus avoiding
cacheline bouncing. -- I'm just not sure how this will work out in relation to
On Sun, Jan 28, 2007 at 12:51:18PM +0100, Peter Zijlstra wrote:
This patch-set breaks up the global file_list_lock which was found to be a
severe contention point under basically any filesystem intensive workload.
Benchmarks, please. Where exactly do you see contention for this?
filesystem
On Sun, Jan 28, 2007 at 12:51:22PM +0100, Peter Zijlstra wrote:
Break the protection of sb-s_files out from under the global file_list_lock.
sb-s_files is converted to a lock_list. furthermore to prevent the
lock_list_head of getting too contended with concurrent add operations
the add is
On Sun, Jan 28, 2007 at 03:11:34PM +0100, Peter Zijlstra wrote:
Eradicate global locks.
- kmap_lock is removed by extensive use of atomic_t, a new flush
scheme and modifying set_page_address to only allow NULL-virt
transitions.
What's the point for this? Extensive atomic_t use is
From: Andrew Morton [EMAIL PROTECTED]
Date: Sat, Jan 27, 2007 at 11:49:28PM -0800
LD init/built-in.o
LD .tmp_vmlinux1
fs/built-in.o: In function `load_elf_binary':
fs/binfmt_elf.c:978: undefined reference to `arch_setup_additional_pages'
make: *** [.tmp_vmlinux1] Error 1
#
#
On Sun, Jan 28, 2007 at 02:43:25PM +, Christoph Hellwig wrote:
On Sun, Jan 28, 2007 at 12:51:18PM +0100, Peter Zijlstra wrote:
This patch-set breaks up the global file_list_lock which was found to be a
severe contention point under basically any filesystem intensive workload.
* Christoph Hellwig [EMAIL PROTECTED] wrote:
On Sun, Jan 28, 2007 at 03:11:34PM +0100, Peter Zijlstra wrote:
Eradicate global locks.
- kmap_lock is removed by extensive use of atomic_t, a new flush
scheme and modifying set_page_address to only allow NULL-virt
transitions.
Denis Vlasenko wrote:
On Friday 26 January 2007 19:23, Bill Davidsen wrote:
Denis Vlasenko wrote:
On Thursday 25 January 2007 21:45, Michael Tokarev wrote:
Phillip Susi wrote:
[...]
But even single-threaded I/O but in large quantities benefits from O_DIRECT
significantly, and I
* Christoph Hellwig [EMAIL PROTECTED] wrote:
On Sun, Jan 28, 2007 at 12:51:22PM +0100, Peter Zijlstra wrote:
Break the protection of sb-s_files out from under the global
file_list_lock.
sb-s_files is converted to a lock_list. furthermore to prevent the
lock_list_head of getting too
* Christoph Hellwig [EMAIL PROTECTED] wrote:
On Sun, Jan 28, 2007 at 12:51:18PM +0100, Peter Zijlstra wrote:
This patch-set breaks up the global file_list_lock which was found
to be a severe contention point under basically any filesystem
intensive workload.
Benchmarks, please.
* Christoph Hellwig [EMAIL PROTECTED] wrote:
On Sun, Jan 28, 2007 at 12:51:21PM +0100, Peter Zijlstra wrote:
This barrier thing is constructed so that it will not write in the
sync() condition (the hot path) when there are no active lock
sections; thus avoiding cacheline bouncing. --
On Sun, Jan 28, 2007 at 04:17:00PM +0100, Ingo Molnar wrote:
scalability. I did lock profiling on the -rt kernel, which exposes such
things nicely. Half of the lock contention events during kernel compile
were due to kmap(). (The system had 2 GB of RAM, so 40% lowmem, 60%
highmem.)
Numbers
On Sun, 2007-01-28 at 15:11 +, Christoph Hellwig wrote:
Even if this is becoming a real problem there must be simpler ways to fix
this than introducing various new locking primitives and all kinds of
complexity.
One good way to fix scalability without all this braindamage is
to get
On Sun, Jan 28, 2007 at 04:21:06PM +0100, Ingo Molnar wrote:
sb-s_files is converted to a lock_list. furthermore to prevent the
lock_list_head of getting too contended with concurrent add
operations the add is buffered in per cpu filevecs.
NACK. Please don't start using lockdep
Denis Vlasenko wrote:
On Saturday 27 January 2007 15:01, Bodo Eggert wrote:
Denis Vlasenko [EMAIL PROTECTED] wrote:
On Friday 26 January 2007 19:23, Bill Davidsen wrote:
Denis Vlasenko wrote:
On Thursday 25 January 2007 21:45, Michael Tokarev wrote:
But even single-threaded I/O but in large
On Sun, 2007-01-28 at 15:30 +, Christoph Hellwig wrote:
On Sun, Jan 28, 2007 at 04:21:06PM +0100, Ingo Molnar wrote:
sb-s_files is converted to a lock_list. furthermore to prevent the
lock_list_head of getting too contended with concurrent add
operations the add is buffered in
On Sun, Jan 28, 2007 at 04:29:04PM +0100, Peter Zijlstra wrote:
I shall pursue this direction. Thanks for the information.
Btw, if you need this short-term there might be an even simpler
solution:
- all files go on sb-s_list and stay there until the file is freed
- ttys grow their private
On Sun, Jan 28, 2007 at 04:24:35PM +0100, Ingo Molnar wrote:
This barrier thing is constructed so that it will not write in the
sync() condition (the hot path) when there are no active lock
sections; thus avoiding cacheline bouncing. -- I'm just not sure how
this will work out in
On Sun, Jan 28, 2007 at 04:32:43PM +0100, Peter Zijlstra wrote:
please see patch 2/7, its unrelated to lockdep internals.
I can't see any 2/7 on lkml yet..
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Am Sun, 28 Jan 2007 09:04:41 +0100 schrieb H. Peter Anvin [EMAIL PROTECTED]:
I think you're confusing the Interrupt Line register and the Interrupt
Pin register. The Interrupt Line register is platform-dependent, but on
x86 platforms it generally contains the IRQ number (and IRQ 0 is valid,
the trivial attached patch fixes ioctl defines in usbdevice_fs.h that are
exported to userspace to use __u32 rather than u32
-mike
pgprIuGYN9qNK.pgp
Description: PGP signature
Use __u32 rather than u32 in userspace ioctl defines.
Signed-off-by: Mike Frysinger [EMAIL PROTECTED]
---
On Fri, Jan 26, 2007 at 12:41:20PM -0800, Andrew Morton wrote:
On Fri, 26 Jan 2007 14:21:42 +0300
Alexey Dobriyan [EMAIL PROTECTED] wrote:
Rewrite via do_utimes() like compat_sys_utime().
I'm somewhat surprised that this wasn't done earlier.
Because, the following patch didn't hit -mm.
On Sat, Jan 27, 2007 at 12:35:42AM +0100, Arnd Bergmann wrote:
On Friday 26 January 2007 21:41, Andrew Morton wrote:
I'm somewhat surprised that this wasn't done earlier. I wonder if there's
some subtle reason why this won't work. How well tested is this?
* Christoph Hellwig [EMAIL PROTECTED] wrote:
NACK. Please don't start using lockdep internals in core code.
what do you mean by that?
struct lock_list is an lockdep implementation detail and should not
leak out and be used anywhere else. [...]
no, it is not. It is a new data
* Christoph Hellwig [EMAIL PROTECTED] wrote:
On Sun, Jan 28, 2007 at 04:17:00PM +0100, Ingo Molnar wrote:
scalability. I did lock profiling on the -rt kernel, which exposes
such things nicely. Half of the lock contention events during kernel
compile were due to kmap(). (The system had 2
Since it seems to be lost in cyberspace
Forwarded Message
From: Peter Zijlstra [EMAIL PROTECTED]
Subject: [PATCH 2/7] lock_list: a fine grain locked double linked list
Date: Sun, 28 Jan 2007 12:51:20 +0100
plain text document attachment (lock_list.patch)
Provide a simple
On Sun, Jan 28, 2007 at 04:48:06PM +0100, Ingo Molnar wrote:
i'm sorry, but do you realize that files_lock is a global lock,
triggered by /every single/ file close?
Please check which thread you're in before you start such lengthy rants.
-
To unsubscribe from this list: send the line
On Sun, Jan 28, 2007 at 11:08:18AM +0100, Jiri Slaby wrote:
Andrew Morton napsal(a):
Temporarily at
http://userweb.kernel.org/~akpm/2.6.20-rc6-mm1/
Unable to select IPV6. Menuconfig doesn't offer it when INET is selected.
When it's not it appears in the menu, but after state change
On Sun, Jan 28, 2007 at 03:30:06PM +, Christoph Hellwig wrote:
On Sun, Jan 28, 2007 at 04:21:06PM +0100, Ingo Molnar wrote:
sb-s_files is converted to a lock_list. furthermore to prevent the
lock_list_head of getting too contended with concurrent add
operations the add is
On Sun, 2007-01-28 at 10:17 +0100, Benny Amorsen wrote:
DB == Dirk Behme [EMAIL PROTECTED] writes:
DB Any chance to have anything like an auto-update mbox archive of
DB LKML? Would be nice for people not permanently subscribed to LKML.
Perhaps nntp://news.gmane.org/gmane.linux.kernel can
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_IA32_EMULATION is not set
Hm Ok. That's explainable. You don't have CONFIG_IA32_EMULATION set
and arch_setup_additional pages is only defined/exported in
syscall32.c which won't be built in your case. (It should go away if
you set
AMD64 with XFS.
IMHO 64 bits are on desktop and laptops over two years. So, i would like
to assign (my small, but maybe not only one due of) 50-70 EUR to help
with new hardware, if you wish.
Actually that's a good idea - why don't we put up a
donation-for-hardware appeal on kernel.org and
Ingo Molnar wrote:
* Christoph Hellwig [EMAIL PROTECTED] wrote:
On Sun, Jan 28, 2007 at 12:51:18PM +0100, Peter Zijlstra wrote:
This patch-set breaks up the global file_list_lock which was found
to be a severe contention point under basically any filesystem
intensive workload.
Benchmarks,
- It seems that people have been busy creating the need for this. I had to
apply over sixty patches to this tree to fix post-2.6.20-rc4-mm1 compilation
errors. And a number of patches were dropped due to no-compile or to
runtime errors. Heaven knows how many runtime bugs were added.
DK == Dave Kleikamp [EMAIL PROTECTED] writes:
DK On Sun, 2007-01-28 at 10:17 +0100, Benny Amorsen wrote:
Perhaps nntp://news.gmane.org/gmane.linux.kernel can help, even if
it isn't exactly what you asked for.
DK I like to read the mailing list this way, but it's not a good
DK method if you
- It seems that people have been busy creating the need for this. I had to
apply over sixty patches to this tree to fix post-2.6.20-rc4-mm1 compilation
errors. And a number of patches were dropped due to no-compile or to
runtime errors. Heaven knows how many runtime bugs were added.
On Sun, Jan 28, 2007 at 08:52:25AM -0800, Martin J. Bligh wrote:
Mmm. not wholly convinced that's true. Whilst i don't have lockmeter
stats to hand, the heavy time in __d_lookup seems to indicate we may
still have a problem to me. I guess we could move the spinlocks out
of line again to test
- It seems that people have been busy creating the need for this. I had to
apply over sixty patches to this tree to fix post-2.6.20-rc4-mm1 compilation
errors. And a number of patches were dropped due to no-compile or to
runtime errors. Heaven knows how many runtime bugs were added.
On Sunday 28 January 2007 16:18, Bill Davidsen wrote:
Denis Vlasenko wrote:
On Friday 26 January 2007 19:23, Bill Davidsen wrote:
Denis Vlasenko wrote:
On Thursday 25 January 2007 21:45, Michael Tokarev wrote:
Phillip Susi wrote:
[...]
But even single-threaded I/O but in
With NO_HZ or HIGH_RES_TIMERS update_process_times() can be called,
when jiffies increments != 1 have to be acounted for.
Cope with these situations by splitting update_process_times() into
__update_process_times() and tick().
New in Take 2 is an attempt to make patch work for SMP also.
This is
release_mem contains two copies of exactly the same code. Refactor
these into a new helper, release_tty. The only change in behaviour
is that the driver reference count is now decremented after the
master tty has been freed instead of before.
Signed-off-by: Christoph Hellwig [EMAIL PROTECTED]
On Sunday 28 January 2007 16:30, Bill Davidsen wrote:
Denis Vlasenko wrote:
On Saturday 27 January 2007 15:01, Bodo Eggert wrote:
Denis Vlasenko [EMAIL PROTECTED] wrote:
On Friday 26 January 2007 19:23, Bill Davidsen wrote:
Denis Vlasenko wrote:
On Thursday 25 January 2007 21:45,
Provide a simple fine grain locked double link list.
It is build upon the regular double linked list primitives, spinlocks and RCU.
Locking is peculiar in that edges are locked, this avoid the circular lock
dependancy created by the fact that the regular linked lists are circular.
Item
Benny Amorsen wrote:
DK == Dave Kleikamp [EMAIL PROTECTED] writes:
DK On Sun, 2007-01-28 at 10:17 +0100, Benny Amorsen wrote:
Perhaps nntp://news.gmane.org/gmane.linux.kernel can help, even if
it isn't exactly what you asked for.
DK I like to read the mailing list this way, but it's not
Christoph Hellwig wrote:
On Sun, Jan 28, 2007 at 08:52:25AM -0800, Martin J. Bligh wrote:
Mmm. not wholly convinced that's true. Whilst i don't have lockmeter
stats to hand, the heavy time in __d_lookup seems to indicate we may
still have a problem to me. I guess we could move the spinlocks out
Marc Perkel wrote:
I'm a little stumped trying to set up raid 10. I set
it up and it worked but after a reboot it forgets my
raid setup.
Created 2 raid 1 arrays in md0 and md1 and that works
and survives a reboot.
However - I created a raid 0 on /dev/md2 made up of
/dev/md0 and /dev/md1 and it
1 - 100 of 498 matches
Mail list logo
