Vincent ETIENNE wrote:
Hi,
Summary :
Got this trace when one network interface come down or up in a 2
interfaces bonding. So far, system seems to survive to this problem
and works fine.
I'm investigating a similar/possibly identical bug. Do you experience
Happy Boxing Day!
If you just turned on your shiny new box and discovered that it's got
an Attansic L1 gigabit ethernet chip in it, and can't get Linux to
recognize it, fear not. Jay and I are still working on getting the
driver ready for merging. A lot of the fancy stuff is un(der)tested,
Christoph Hellwig wrote:
On Wed, Jan 10, 2007 at 06:40:51PM -0600, Jay Cliburn wrote:
--- /dev/null
+++ b/drivers/net/atl1/Makefile
@@ -0,0 +1,30 @@
+
+#
+# Attansic L1 gigabit ethernet driver
+# Copyright(c) 2005 -
While pondering ways to optimize I/O and swapping on large NUMA machines, I
noticed that the numa_node field in struct device isn't actually used anywhere.
We just have a couple dozen lines of code to conditionally create a sysfs file
that will always return -1. Is anyone even working on code
Yinghai Lu wrote:
why not rename relocs.c to relocs_32.c?
Because we're trying to get rid of all the _32 and _64 files?
-- Chris
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Yinghai Lu wrote:
On Jan 31, 2008 12:33 AM, Chris Snook [EMAIL PROTECTED] wrote:
Yinghai Lu wrote:
why not rename relocs.c to relocs_32.c?
Because we're trying to get rid of all the _32 and _64 files?
but that file is not need for x86_64
Which means there's no conflict with any 64-bit
Lars Noschinski wrote:
Hello!
For an university project, we had to write a toy filesystem (ext2-like),
for which I would like to implement sparse file support. For this, I
digged through the ext2 source code; but I could not find the point,
where ext2 detects holes.
As far as I can see from
veerasena reddy wrote:
I have a requirement where i need to execute a user process even when
the kernel is utilizing 100% of CPU time.
In the realtime kernel, hardware interrupt handlers are prioritized
threads, so you can give the userspace process a higher realtime priority.
--
Gene Heskett wrote:
Greetings;
I just rebooted to a new config of 2.6.24, basically trying to strip out the
building of modules I don't use. And I enabled a couple of checks that
weren't checked in the kernel-hacking menu. .config posted on request.
Now the messages log is being spammed
Jay Cliburn wrote:
On Tue, 22 Jan 2008 04:56:11 -0500
Jeff Garzik [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
From: Jay Cliburn [EMAIL PROTECTED]
Update initialization parameters to match the current vendor driver
version 1.2.40.2.
[...]
ACK without any better knowledge... but is
Al Boldi wrote:
Greetings!
data=ordered mode has proven reliable over the years, and it does this by
ordering filedata flushes before metadata flushes. But this sometimes
causes contention in the order of a 10x slowdown for certain apps, either
due to the misuse of fsync or due to inherent
?
This satisfies me.
Acked-by: Chris Snook [EMAIL PROTECTED]
From df475e2eea401f9dc18ca23dab538b99fb9e710c Mon Sep 17 00:00:00 2001
From: Jay Cliburn [EMAIL PROTECTED]
Date: Wed, 23 Jan 2008 21:36:36 -0600
Subject: [PATCH] atl1: simplify tx packet descriptor
The transmit packet descriptor
From: Chris Snook [EMAIL PROTECTED]
Make MARKERS depend on MODULES to prevent build failures with certain configs.
Signed-off-by: Chris Snook [EMAIL PROTECTED]
diff --git a/init/Kconfig b/init/Kconfig
index dcef8b5..933df15 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -729,6 +729,7 @@ config
Andre Noll wrote:
we are experiencing massive performance problems with two of our
Linux servers that contain 3ware controllers on a Tyan mainboard and
a couple of 1T disks.
During the daily cron job that uses rsync to sync a 500G file system
from another machine to the raid on the 3ware
Latchesar Ionkov wrote:
Sample ramfs file server that uses the in-kernel 9P file server support.
This code is for reference only.
Reference code generally goes in Documentation/
-- Chris
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
Zurk Tech wrote:
dmesg (new) with disabled GART error reporting if anyone wants to
compare to previous dmesg with GART error reporting :
A few unrelated observations about Barcelona support...
Marking TSC unstable due to TSCs unsynchronized
This is probably wrong. The TSC is on the
Don Porter wrote:
From: Donald E. Porter [EMAIL PROTECTED]
In the bulk page allocation/free routines in mm/page_alloc.c, the zone
lock is held across all iterations. For certain parallel workloads, I
have found that releasing and reacquiring the lock for each iteration
yields better
ciol wrote:
Hi, I'd like to ask you a few questions:
* Do you like the way linux distributions integrate the kernel?
* Wouldn't you prefer they ship with the stable and still maintained
2.6.16.X, while providing optionally the latest kernel for those who
want or just have a new hardware?
*
Benny Halevy wrote:
Greetings,
I would like to hear peoples opinion about the indentation convention
described below that I personally found the most practical with
several different editors.
The gist of it is that tabs should be used for nesting, not for decoration.
Indent your code with as
ciol wrote:
Chris Snook wrote:
Why are you asking the developers? We do this for the sake of the users.
The kernel is the software of the developers.
The kernel is a technology. A distribution is a product. When decisions about
technology and decisions about products are made
Peter Zijlstra wrote:
Hi Tim,
On Wed, 2007-07-11 at 15:37 -0700, Tim Pepper wrote:
On 7/9/07, Peter Zijlstra [EMAIL PROTECTED] wrote:
Use the read-ahead code to provide hints to page reclaim.
This patch has the potential to solve the streaming-IO trashes my
desktop problem.
It tries to
Jack Stone wrote:
I hope I got the CC list right. Apologies to anyone in didn't include
and anyone I shouldn't have included.
The basic idea is to include an idea from VMS that seems to be quite
useful: version numbers for files.
The idea is that whenever you modify a file the system saves it
Jack Stone wrote:
Chris Snook wrote:
The underlying internal implementation of something like this wouldn't
be all that hard on many filesystems, but it's the interface that's the
problem. The ':' character is a perfectly legal filename character, so
doing it that way would break things
Jack Stone wrote:
Chris Snook wrote:
But what you're talking about *will* break userspace. If I do an ls in
a directory, and get pages upon pages of versions of just one file,
that's broken. If I tar up a directory and get a tarball that's
hundreds of times larger than it should be, that's
Jack Stone wrote:
H. Peter Anvin wrote:
Chris Snook wrote:
I pointed out NetApp's .snapshot directories because that's a method
that uses legal path character, but doesn't break anything. With this
method, userspace tools will have to be taught that : is suddenly a
special character
Jack Stone wrote:
Chris Snook wrote:
Jack Stone wrote:
The idea was that if you did an ls you would get the latest version of
the file without the :revision_num. The only visible version would be
the latest version, i.e. the current system would not change. The idea
was that it would only show
Jack Stone wrote:
Chris Snook wrote:
Jack Stone wrote:
H. Peter Anvin wrote:
Chris Snook wrote:
I pointed out NetApp's .snapshot directories because that's a method
that uses legal path character, but doesn't break anything. With this
method, userspace tools will have to be taught
Joshua David Williams wrote:
I've been keeping tabs on the GPLv3 dispute for quite some time. It seems to
me that the best solution would be for us to write our own open source
license - one that would be written specifically to uphold the ten rights in
the open source definition.
Your
Bryan Henderson wrote:
The directory is quite visible with a standard 'ls -a'. Instead,
they simply mark it as a separate volume/filesystem: i.e. the fsid
differs when you call stat(). The whole thing ends up acting rather like
our bind mounts.
Hmm. So it breaks user space quite a bit. By
Zoltán HUBERT wrote:
Hello gentlemen (and ladies ?)
As a power-user (NOT a hacker) I kindly ask you to please
change the naming scheme and come back to the traditional
model, and release a stable kernel while working on a
develoment branch.
I'm not on the [lkml] so should you answer please
From: Chris Snook [EMAIL PROTECTED]
Clean up whitespace and comments in drivers/serial/icom.c
Signed-off-by: Chris Snook [EMAIL PROTECTED]
The patch is very large (30k) so I have attached it. Please let me know if you
really, really want it inline.
--- a/drivers/serial/icom.c 2007-06-05 16
Paul Mackerras wrote:
Chris Snook writes:
Clean up whitespace and comments in drivers/serial/icom.c
These changes seem totally unnecessary, as the existing indentation is
according to a commonly-accepted style and is quite reasonable:
There are actually a few different indentation styles
Luca Tettamanti wrote:
Il Mon, Jun 25, 2007 at 07:42:44AM -0500, Jay Cliburn ha scritto:
Jay L. T. Cornwall wrote:
Jay Cliburn wrote:
For reasons not yet clear to me, it appears the L1 driver has a bug or
the device itself has trouble with DMA in high memory. This patch,
drafted by Luca
Jay L. T. Cornwall wrote:
Chris Snook wrote:
What boards have we seen this on? It's quite possible this is:
I can reproduce on an Asus P5K with a Core 2 Duo E6600.
lspci identifies the controller as:
02:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit
Ethernet Adapter
Jeff Garzik wrote:
Jay Cliburn wrote:
On Mon, 25 Jun 2007 17:57:20 -0400
Chris Snook [EMAIL PROTECTED] wrote:
Jay L. T. Cornwall wrote:
Chris Snook wrote:
What boards have we seen this on? It's quite possible this is:
I can reproduce on an Asus P5K with a Core 2 Duo E6600.
lspci
Oleg Nesterov wrote:
on top of sys_time-speedup.patch
Ingo Molnar wrote:
asmlinkage long sys_time(time_t __user * tloc)
{
- time_t i;
- struct timeval tv;
+ /*
+* We read xtime.tv_sec atomically - it's updated
+* atomically by update_wall_time(), so no need
Oleg Nesterov wrote:
On 06/26, Chris Snook wrote:
Oleg Nesterov wrote:
on top of sys_time-speedup.patch
Ingo Molnar wrote:
asmlinkage long sys_time(time_t __user * tloc)
{
- time_t i;
- struct timeval tv;
+ /*
+* We read xtime.tv_sec atomically - it's updated
Krzysztof Oledzki wrote:
On Sat, 30 Jun 2007, Arjan van de Ven wrote:
On Sat, 2007-06-30 at 16:55 +0200, Krzysztof Oledzki wrote:
Hello,
It seems that IRQ handling is somehow different between i386 and x86_64.
In my Dell PowerEdge 1950 is it possible to enable interrupts spreading
over
[EMAIL PROTECTED] wrote:
---
I have Pentium D CPU, which many Windows utilities like cpuz, wcpuid,
everest identify as D 930 (Dual Core, 3GHz). From Intel site I find out
that it has no HT feature, nor Windows XP identify
[EMAIL PROTECTED] wrote:
On Fri, 18 May 2007, Chris Snook wrote:
[EMAIL PROTECTED] wrote:
---
I have Pentium D CPU, which many Windows utilities like cpuz, wcpuid,
everest identify as D 930 (Dual Core, 3GHz). From
Jay Cliburn wrote:
Please accept the following trivial patches to the atl1 driver.
- use dev_printk macros
- fix whitespace damage
Acked-By: Chris Snook [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
., nic-de...@qualcomm.com);
-MODULE_DESCRIPTION(Qualcom Atheros 100/1000M Ethernet Network Driver);
+MODULE_DESCRIPTION(Qualcomm Atheros 100/1000M Ethernet Network Driver);
MODULE_LICENSE(GPL);
MODULE_VERSION(ATL1C_DRV_VERSION);
Acked-by: Chris Snook chris.sn...@gmail.com
--
To unsubscribe from
Happy Boxing Day!
If you just turned on your shiny new box and discovered that it's got
an Attansic L1 gigabit ethernet chip in it, and can't get Linux to
recognize it, fear not. Jay and I are still working on getting the
driver ready for merging. A lot of the fancy stuff is un(der)tested,
Christoph Hellwig wrote:
On Wed, Jan 10, 2007 at 06:40:51PM -0600, Jay Cliburn wrote:
--- /dev/null
+++ b/drivers/net/atl1/Makefile
@@ -0,0 +1,30 @@
+
+#
+# Attansic L1 gigabit ethernet driver
+# Copyright(c) 2005 -
Al Viro wrote:
NB: driver is choke-full of code that will break on big-endian; as long
as the hardware is onboard-only we can live with that, but sooner or
later that'll need fixing.
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
---
drivers/net/atl1/atl1_main.c |4 ++--
1 files changed, 2
Paa Paa wrote:
I'm using Linux 2.6.20.4. I noticed that I get lower SATA hard drive
throughput with 2.6.20.4 than with 2.6.19. The reason was that 2.6.20
enables NCQ by defauly (queue_depth = 31/32 instead of 0/32). Transfer
rate was measured using "hdparm -t":
With NCQ (queue_depth == 31):
Linus Torvalds wrote:
On Thu, 5 Apr 2007, Robin Holt wrote:
For testing, Jack Steiner create the following patch. All it does
is moves tasks which are transitioning to the zombie state from where
they are in the children list to the head of the list. In this way,
they will be the first found
Chris Snook wrote:
Linus Torvalds wrote:
On Thu, 5 Apr 2007, Robin Holt wrote:
For testing, Jack Steiner create the following patch. All it does
is moves tasks which are transitioning to the zombie state from where
they are in the children list to the head of the list. In this way
Eric W. Biederman wrote:
Linus Torvalds <[EMAIL PROTECTED]> writes:
I'm not sure anybody would really be unhappy with pptr pointing to some
magic and special task that has pid 0 (which makes it clear to everybody
that the parent is something special), and that has SIGCHLD set to SIG_IGN
Al Viro wrote:
Spot the bug...
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
---
diff --git a/drivers/net/atl1/atl1_hw.c b/drivers/net/atl1/atl1_hw.c
index 08b2d78..e28707a 100644
--- a/drivers/net/atl1/atl1_hw.c
+++ b/drivers/net/atl1/atl1_hw.c
@@ -357,7 +357,7 @@ void atl1_hash_set(struct
v j wrote:
You don't get it do you. Our source code is meaningless to the Open
Source community at large. It is only useful to our tiny set of
competitors that have nothing to do with Linux. The Embedded space is
very specific. We are only _using_ Linux. Just as we could have used
VxWorks or
The generic lseek code in fs/read_write.c uses hardcoded values for
SEEK_{SET,CUR,END}.
Patch 1 fixes the case statements to use the symbolic constants in
include/linux/fs.h, and should not be at all controversial.
Patch 2 adds a SEEK_MAX and uses it to validate user arguments. This makes
the
From: Chris Snook <[EMAIL PROTECTED]>
Convert magic numbers to SEEK_* values from fs.h
Signed-off-by: Chris Snook <[EMAIL PROTECTED]>
--
--- a/fs/read_write.c 2007-02-20 14:49:45.0 -0500
+++ b/fs/read_write.c 2007-02-20 16:48:39.0 -0500
@@ -37,10 +37,
From: Chris Snook <[EMAIL PROTECTED]>
Add SEEK_MAX and use it to validate lseek arguments from userspace.
Signed-off-by: Chris Snook <[EMAIL PROTECTED]>
--
diff -urp b/fs/read_write.c c/fs/read_write.c
--- b/fs/read_write.c 2007-02-20 16:48:39.0 -0500
+++ c/fs/read_write.c
Jack Stone wrote:
I hope I got the CC list right. Apologies to anyone in didn't include
and anyone I shouldn't have included.
The basic idea is to include an idea from VMS that seems to be quite
useful: version numbers for files.
The idea is that whenever you modify a file the system saves it
Jack Stone wrote:
Chris Snook wrote:
The underlying internal implementation of something like this wouldn't
be all that hard on many filesystems, but it's the interface that's the
problem. The ':' character is a perfectly legal filename character, so
doing it that way would break things
LAPLACE Cyprien wrote:
An example: in kernel/pid.c:alloc_pid(), if one of the guest CPUs is
descheduled when holding the pidmap_lock, what happens to the other
guest CPUs who want to alloc/free pids ? Are they blocked too ?
Yup. This is where it's really nice to have directed yields, where
Vincent ETIENNE wrote:
Hi,
Summary :
Got this trace when one network interface come down or up in a 2
interfaces bonding. So far, system seems to survive to this problem
and works fine.
I'm investigating a similar/possibly identical bug. Do you experience
अभिजित भोपटकर (Abhijit Bhopatkar) wrote:
The mm structures of interactive tasks are marked and
the pages belonging to them are never shifted to inactive
list in lru algorithm. Thus keeping interactive tasks in
memory as long as possible.
The interactivity is already determined by schedular so
we
From: Chris Snook <[EMAIL PROTECTED]>
Clean up whitespace and comments in drivers/serial/icom.c
Signed-off-by: Chris Snook <[EMAIL PROTECTED]>
The patch is very large (30k) so I have attached it. Please let me know if you
really, really want it inline.
--- a/drivers/serial/ic
Paul Mackerras wrote:
Chris Snook writes:
Clean up whitespace and comments in drivers/serial/icom.c
These changes seem totally unnecessary, as the existing indentation is
according to a commonly-accepted style and is quite reasonable:
There are actually a few different indentation styles
[EMAIL PROTECTED] wrote:
---
I have Pentium D CPU, which many Windows utilities like cpuz, wcpuid,
everest identify as D 930 (Dual Core, 3GHz). From Intel site I find out
that it has no HT feature, nor Windows XP identify
[EMAIL PROTECTED] wrote:
On Fri, 18 May 2007, Chris Snook wrote:
[EMAIL PROTECTED] wrote:
---
I have Pentium D CPU, which many Windows utilities like cpuz, wcpuid,
everest identify as D 930 (Dual Core, 3GHz). From
Jay Cliburn wrote:
Please accept the following trivial patches to the atl1 driver.
- use dev_printk macros
- fix whitespace damage
Acked-By: Chris Snook <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Peter Zijlstra wrote:
Hi Tim,
On Wed, 2007-07-11 at 15:37 -0700, Tim Pepper wrote:
On 7/9/07, Peter Zijlstra <[EMAIL PROTECTED]> wrote:
Use the read-ahead code to provide hints to page reclaim.
This patch has the potential to solve the streaming-IO trashes my
desktop problem.
It tries to
Jack Stone wrote:
Chris Snook wrote:
But what you're talking about *will* break userspace. If I do an ls in
a directory, and get pages upon pages of versions of just one file,
that's broken. If I tar up a directory and get a tarball that's
hundreds of times larger than it should be, that's
Jack Stone wrote:
H. Peter Anvin wrote:
Chris Snook wrote:
I pointed out NetApp's .snapshot directories because that's a method
that uses legal path character, but doesn't break anything. With this
method, userspace tools will have to be taught that : is suddenly a
special character
Jack Stone wrote:
Chris Snook wrote:
Jack Stone wrote:
The idea was that if you did an ls you would get the latest version of
the file without the :revision_num. The only visible version would be
the latest version, i.e. the current system would not change. The idea
was that it would only show
Jack Stone wrote:
Chris Snook wrote:
Jack Stone wrote:
H. Peter Anvin wrote:
Chris Snook wrote:
I pointed out NetApp's .snapshot directories because that's a method
that uses legal path character, but doesn't break anything. With this
method, userspace tools will have to be taught
Joshua David Williams wrote:
I've been keeping tabs on the GPLv3 dispute for quite some time. It seems to
me that the best solution would be for us to write our own open source
license - one that would be written specifically to uphold the ten rights in
the open source definition.
Your
Bryan Henderson wrote:
The directory is quite visible with a standard 'ls -a'. Instead,
they simply mark it as a separate volume/filesystem: i.e. the fsid
differs when you call stat(). The whole thing ends up acting rather like
our bind mounts.
Hmm. So it breaks user space quite a bit. By
Zoltán HUBERT wrote:
Hello gentlemen (and ladies ?)
As a power-user (NOT a hacker) I kindly ask you to please
change the naming scheme and come back to the traditional
model, and release a stable kernel while working on a
develoment branch.
I'm not on the [lkml] so should you answer please
Luca Tettamanti wrote:
Il Mon, Jun 25, 2007 at 07:42:44AM -0500, Jay Cliburn ha scritto:
Jay L. T. Cornwall wrote:
Jay Cliburn wrote:
For reasons not yet clear to me, it appears the L1 driver has a bug or
the device itself has trouble with DMA in high memory. This patch,
drafted by Luca
Jay L. T. Cornwall wrote:
Chris Snook wrote:
What boards have we seen this on? It's quite possible this is:
I can reproduce on an Asus P5K with a Core 2 Duo E6600.
lspci identifies the controller as:
02:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit
Ethernet Adapter
Jeff Garzik wrote:
Jay Cliburn wrote:
On Mon, 25 Jun 2007 17:57:20 -0400
Chris Snook <[EMAIL PROTECTED]> wrote:
Jay L. T. Cornwall wrote:
Chris Snook wrote:
What boards have we seen this on? It's quite possible this is:
I can reproduce on an Asus P5K with a Core 2 Duo E6600.
Oleg Nesterov wrote:
on top of sys_time-speedup.patch
Ingo Molnar wrote:
asmlinkage long sys_time(time_t __user * tloc)
{
- time_t i;
- struct timeval tv;
+ /*
+* We read xtime.tv_sec atomically - it's updated
+* atomically by update_wall_time(), so no need
Oleg Nesterov wrote:
On 06/26, Chris Snook wrote:
Oleg Nesterov wrote:
on top of sys_time-speedup.patch
Ingo Molnar wrote:
asmlinkage long sys_time(time_t __user * tloc)
{
- time_t i;
- struct timeval tv;
+ /*
+* We read xtime.tv_sec atomically - it's updated
Satyam Sharma wrote:
[ Just cleaning up my inbox, and stumbled across this thread ... ]
On 5/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Introduce CONFIG_STABLE to control checks only useful for development.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
[...]
menu "General
Satyam Sharma wrote:
On 7/20/07, Chris Snook <[EMAIL PROTECTED]> wrote:
Satyam Sharma wrote:
> [ Just cleaning up my inbox, and stumbled across this thread ... ]
>
>
> On 5/31/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> Introduce CONFIG_STABLE
Satyam Sharma wrote:
On 7/20/07, Chris Snook <[EMAIL PROTECTED]> wrote:
Satyam Sharma wrote:
> On 7/20/07, Chris Snook <[EMAIL PROTECTED]> wrote:
>> Satyam Sharma wrote:
>> > [ Just cleaning up my inbox, and stumbled across this thread ... ]
>> >
>>
Tong Li wrote:
This patch extends CFS to achieve better fairness for SMPs. For example,
with 10 tasks (same priority) on 8 CPUs, it enables each task to receive
equal CPU time (80%). The code works on top of CFS and provides SMP
fairness at a coarser time grainularity; local on each CPU, it
Herbert Xu wrote:
On Wed, Aug 15, 2007 at 01:02:23PM -0400, Chris Snook wrote:
Herbert Xu wrote:
Andi Kleen <[EMAIL PROTECTED]> wrote:
My config with march=pentium-m and gcc (GCC) 4.1.2 (Gentoo 4.1.2):
textdata bss dec hex filename
3434150 249176 176128 3859454
Ilpo Järvinen wrote:
On Thu, 16 Aug 2007, Herbert Xu wrote:
We've been through that already. If it's a busy-wait it
should use cpu_relax.
I looked around a bit by using some command lines and ended up wondering
if these are equal to busy-wait case (and should be fixed) or not:
Herbert Xu wrote:
On Thu, Aug 16, 2007 at 10:06:31AM +0200, Stefan Richter wrote:
Do you (or anyone else for that matter) have an example of this?
The only code I somewhat know, the ieee1394 subsystem, was perhaps
authored and is currently maintained with the expectation that each
occurrence
Ilpo Järvinen wrote:
On Thu, 16 Aug 2007, Herbert Xu wrote:
We've been through that already. If it's a busy-wait it
should use cpu_relax.
I looked around a bit by using some command lines and ended up wondering
if these are equal to busy-wait case (and should be fixed) or not:
sk malik wrote:
Solaris 10 people are talkin a lot about the
predictive self healing thing.
Do we have something similar planned/going on for
linux. Or there is no use of this tecnology ;)
Doing this in-kernel would violate the separation of policy and
mechanism. There's nothing wrong with
Anand Jahagirdar wrote:
Hello All
I have searched for Maintainers List to get the correct
Maintainer for my patch. But i am not getting exact maintainer to
which i should forward my patch. Will any body please tell me,to which
maintainer i should forward my patch for its inclusion?
Herbert Xu wrote:
On Thu, Aug 16, 2007 at 03:48:54PM -0400, Chris Snook wrote:
Can you find an actual atomic_read code snippet there that is
broken without the volatile modifier?
A whole bunch of atomic_read uses will be broken without the volatile
modifier once we start removing barriers
Joe Perches wrote:
I've got a tree with a directory full of separate
MAINTAINER blocks that looks like:
00_file_description
3c359_network_driver
3c505_network_driver
3c59x_network_driver
3cr990_network_driver
...
zd1211rw_wireless_driver
zf_machz_watchdog
zr36067_video_for_linux_driver
Linus Torvalds wrote:
So the only reason to add back "volatile" to the atomic_read() sequence is
not to fix bugs, but to _hide_ the bugs better. They're still there, they
are just a lot harder to trigger, and tend to be a lot subtler.
What about barrier removal? With consistent semantics we
Stefan Richter wrote:
Nick Piggin wrote:
Stefan Richter wrote:
Nick Piggin wrote:
I don't know why people would assume volatile of atomics. AFAIK, most
of the documentation is pretty clear that all the atomic stuff can be
reordered etc. except for those that modify and return a value.
Christoph Lameter wrote:
On Fri, 17 Aug 2007, Paul E. McKenney wrote:
On Sat, Aug 18, 2007 at 08:09:13AM +0800, Herbert Xu wrote:
On Fri, Aug 17, 2007 at 04:59:12PM -0700, Paul E. McKenney wrote:
gcc bugzilla bug #33102, for whatever that ends up being worth. ;-)
I had totally forgotten
Herbert Xu wrote:
On Mon, Aug 20, 2007 at 09:15:11AM -0400, Chris Snook wrote:
Linus Torvalds wrote:
So the only reason to add back "volatile" to the atomic_read() sequence is
not to fix bugs, but to _hide_ the bugs better. They're still there, they
are just a lot harder to trigger
Anand Jahagirdar wrote:
Hi
As Per the Previous Discussion of my Patch,I think insted of using
KERN_CRIT,it is better to lower the priority level to KERN_WARNING.
thats why i used KERN_WARNING.it will warn administrator and its
administrator responsibility to take whatever action he want to
Joe Perches wrote:
On Sat, 2007-08-18 at 13:35 -0400, Robert P. J. Day wrote:
$ show_subsystem drivers/bluetooth/bpa10x.c
BLUETOOTH
"what's a subsystem"?
I'm not sure there is an appropriate definition.
If there is an appropriate definition, why
should anyone care what subsystem a
David Miller wrote:
From: Linus Torvalds <[EMAIL PROTECTED]>
Date: Mon, 20 Aug 2007 22:46:47 -0700 (PDT)
Ie a "barrier()" is likely _cheaper_ than the code generation downside
from using "volatile".
Assuming GCC were ever better about the code generation badness
with volatile that has been
Joe Perches wrote:
On Mon, 2007-08-20 at 15:31 -0400, Chris Snook wrote:
Until I can pass a patch or source file as an argument to a script and get out
the URL of the git tree it needs to go into on the path to Linus's tree,
MAINTAINERS is inadequate. If I ask for the MAINTAINER info
Hirokazu Takata wrote:
I think the parameter of atomic_read() should have "const"
qualifier to avoid these warnings, and IMHO this modification might be
worth applying on other archs.
I agree.
Here is an additional patch to revise the previous one for m32r.
I'll incorporate this change if
Krzysztof Halasa wrote:
Hi,
"Anand Jahagirdar" <[EMAIL PROTECTED]> writes:
I am forwarding one more improved patch which i have modified as
per your suggestions. Insted of KERN_INFO i have used KERN_NOTICE and
i have added one more if block to check hard limit. how good it is?
Not very,
Denys Vlasenko wrote:
On Friday 24 August 2007 18:06, Christoph Lameter wrote:
On Fri, 24 Aug 2007, Satyam Sharma wrote:
But if people do seem to have a mixed / confused notion of atomicity
and barriers, and if there's consensus, then as I'd said earlier, I
have no issues in going with the
201 - 300 of 488 matches
Mail list logo
