--- Al Viro <[EMAIL PROTECTED]> wrote:
> On Sat, Aug 18, 2007 at 10:20:34PM -0700, Marc
> Perkel wrote:
> > Let me give you and example of the difference
> between
> > Linux open source world brain damaged thinking and
> > what it's like out here in the real world.
>
> [snip]
>
> Marc, why don'
On Sat, Aug 18, 2007 at 10:20:34PM -0700, Marc Perkel wrote:
> Let me give you and example of the difference between
> Linux open source world brain damaged thinking and
> what it's like out here in the real world.
[snip]
Marc, why don't you do the obvious thing and hire Jeff Merkey?
He used to w
Chris Wright wrote:
* Chris Wright ([EMAIL PROTECTED]) wrote:
Now that I understand the problem, I do have a very simple (slightly
overkill) fix for paravirt patching. This can be cleaned up to avoid
the copies when they aren't needed, but that will take a little more
auditing of the various
From: Al Viro <[EMAIL PROTECTED]>
Date: Sun, 19 Aug 2007 04:51:26 +0100
>
> Signed-off-by: Al Viro <[EMAIL PROTECTED]>
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
Thanks for catching this Al.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messa
Let me give you and example of the difference between
Linux open source world brain damaged thinking and
what it's like out here in the real world.
Go to a directory with 10k files and type:
rm *
What do you get?
/bin/rm: Argument list too long
If you map a network drive in DOS and type:
del
I'm running an Athlon64 x2 system which regularly issues general
protection faults and later crashes whenever frequency scaling is
enabled.
If the system runs at full frequency all the time (eg "performance"
govenor), even with powernow-k8 and other governors loaded, it is
perfectly stable.
When
No Al, there isn't any shortage of arrogance here.
Let me try to repeat what I'm talking about as simply
as I can.
First - I'm describing a kind of functionality and
suggesting Linux should have it. I know a lot of it
can be done because much of what I'm suggesting is
already working in Windows a
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
---
diff --git a/net/bridge/br_sysfs_br.c b/net/bridge/br_sysfs_br.c
index 88f4300..c65f54e 100644
--- a/net/bridge/br_sysfs_br.c
+++ b/net/bridge/br_sysfs_br.c
@@ -167,6 +167,7 @@ static ssize_t store_stp_state(struct device *d,
br_stp_set_enable
Chris Wright wrote:
* Chris Wright ([EMAIL PROTECTED]) wrote:
Now that I understand the problem, I do have a very simple (slightly
overkill) fix for paravirt patching. This can be cleaned up to avoid
the copies when they aren't needed, but that will take a little more
auditing of the various
On Sat, Aug 18, 2007 at 07:03:06PM -0700, [EMAIL PROTECTED] wrote:
> >>I suspect you will find it somewhat hard to convince *anybody* on
> >>this list to put either a regex engine or a Perl interpreter into the
> >>kernel. I doubt you could even get a simple shell-style pattern
> >>matcher in. Fi
On Sat, 18 Aug 2007, Alan wrote:
On Wed, 2007-08-15 at 13:22 -0400, Kyle Moffett wrote:
On Aug 15, 2007, at 13:09:31, Marc Perkel wrote:
The idea is that people have permissions - not files. By people I
mean users, groups, managers, applications
etc. One might even specify that there are no p
I am running kernel 2.6.21 on my realview_eb_mpcore system.
at the beginning I found the program is stuck at calibrating
loop, this is because that the timer0 didn't give out
any interrupt.
after enable the timer0's interrupt, I found that even when there is
no timer interrupt the
On Sat, Aug 18, 2007 at 12:22:26PM -0500, Matt Mackall wrote:
> > > > So VSZ:RSS ratio actually goes up with memory pressure.
> > >
> > > And yes.
> > >
> > > But that's not what I'm talking about. You're likely to have more
> > > holes in your ranges with memory pressure as things that aren'
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 particular
file is in?
> 1
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
---
diff --git a/include/math-emu/soft-fp.h b/include/math-emu/soft-fp.h
index a0721ef..a6f873b 100644
--- a/include/math-emu/soft-fp.h
+++ b/include/math-emu/soft-fp.h
@@ -98,7 +98,7 @@
#endif
#ifndef FP_TRAPPING_EXCEPTIONS
-#define FP_TRAPPING_EXCPET
Hi all,
We would like to ask you a few questions about your use of the GIT
version control system. This survey is mainly to understand who is
using GIT, how and why.
The results will be discussed on the git mailing list and published to
the GIT wiki at http://git.or.cz/gitwiki/GitSurvey2007
We'
Those BUG_ON's were there because of past bugs and fragility in the
de_thread and exit synchronization stuff. There's no real need to leave
them (in fixed form) if we are confident of that stuff working right now,
or have other assertions to give us that confidence when we change it.
Thanks,
Rol
On Wed, 2007-08-15 at 10:34 -0700, Marc Perkel wrote:
> Keep in mind that this is about thinking outside the
> box. Don't let new ideas scare you.
My cat thinks outside the box all the time. Cleaning it up is a real
pain.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Maybe it can use wait_task_inactive, which IIUC is being changed to address
the same RT issue. OTOH, notify_count exists only for this. So maybe the
better way is to clean that whole mechanism up somehow. The exit.c changes
in your patch seem to be making it more mysterious rather than less so.
On Wed, 2007-08-15 at 13:22 -0400, Kyle Moffett wrote:
> On Aug 15, 2007, at 13:09:31, Marc Perkel wrote:
> > The idea is that people have permissions - not files. By people I
> > mean users, groups, managers, applications
> > etc. One might even specify that there are no permission
> > restri
>
> Neil, please, don't add tasklist_lock again. It was not easy to wipe it from
> fs/proc/ :) Just change this code to use rcu_read_lock().
>
Ok, done/tested. Thanks!
Currently, there exists no method for a process to query the resource
limits of another process. They can be inferred via som
On Sat, Aug 18, 2007 at 03:41:13PM -0700, Linus Torvalds wrote:
>
>
> On Sat, 18 Aug 2007, Paul E. McKenney wrote:
> >
> > One of the gcc guys claimed that he thought that the two-instruction
> > sequence would be faster on some x86 machines. I pointed out that
> > there might be a concern abou
> - ENOMEM still can happen after de_thread(), ->sighand is not the last
> object we have to allocate
As long as this is true, I think it's the incontrovertible argument there
is no reason not to simplify it. (Not that I don't also agree with your
other reasons).
Thanks,
Roland
-
> There is no any reason to do recalc_sigpending() after changing ->sighand.
> To begin with, recalc_sigpending() does not take ->sighand into account.
I agree. I think that call dates from before some other cleanups in that
code, when ->signal was changed there. At the time, it was the most
con
On Sat, 18 Aug 2007, Paul E. McKenney wrote:
>
> One of the gcc guys claimed that he thought that the two-instruction
> sequence would be faster on some x86 machines. I pointed out that
> there might be a concern about code size. I chose not to point out
> that people might also care about the
On Sat, Aug 18, 2007 at 09:39:36PM +0400, Oleg Nesterov wrote:
> de_thread:
>
> if (atomic_read(&oldsighand->count) <= 1)
> BUG_ON(atomic_read(&sig->count) != 1);
>
> This is not safe without the rmb() in between. The results of two correctly
> ordered __exit_signal()->atomic_
* Chris Wright ([EMAIL PROTECTED]) wrote:
> Now that I understand the problem, I do have a very simple (slightly
> overkill) fix for paravirt patching. This can be cleaned up to avoid
> the copies when they aren't needed, but that will take a little more
> auditing of the various patchers. If you
On Fri, Aug 17, 2007 at 01:48:09PM -0500, Corey Minyard wrote:
> Paul E. McKenney wrote:
> >On Fri, Aug 17, 2007 at 09:56:45AM +0200, Peter Zijlstra wrote:
> >
> >>On Thu, 2007-08-16 at 09:01 -0700, Paul E. McKenney wrote:
> >>
> >>>On Thu, Aug 16, 2007 at 04:25:07PM +0200, Peter Zijlstra wro
Andi Kleen wrote:
>> This patch breaks Xen booting.
>>
>
> Check the latest git head. Does it still break?
Yes, that's with latest git head.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Fri, Aug 17, 2007 at 06:24:15PM -0700, 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 w
On Fri, Aug 17, 2007 at 09:13:35PM -0700, Linus Torvalds wrote:
>
>
> On Sat, 18 Aug 2007, Satyam Sharma wrote:
> >
> > No code does (or would do, or should do):
> >
> > x.counter++;
> >
> > on an "atomic_t x;" anyway.
>
> That's just an example of a general problem.
>
> No, you don't us
* Linus Torvalds ([EMAIL PROTECTED]) wrote:
> On Sat, 18 Aug 2007, Chris Wright wrote:
> > >
> > > Check the latest git head. Does it still break?
> >
> > Yeah, this is the latest git. The broken commit is Rusty's patch which,
> > after Linus reverted the write-protected remap changes, is no lon
On 8/18/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>
> On Aug 18 2007 14:22, Robert Hancock wrote:
> >> I see this a a very important feature in the embedded system relm, I
> >> have worked on two projects that required extreme power management,
> >> and massive data storage. The ability to ful
On Aug 18 2007 14:22, Robert Hancock wrote:
>> I see this a a very important feature in the embedded system relm, I
>> have worked on two projects that required extreme power management,
>> and massive data storage. The ability to fully turn off a drive while
>> the system is running is key. It s
On Aug 18 2007 22:01, Xu Yang wrote:
>
>this vmlinux file is running on my software virtual prototype system.
>and my software enviorment can only load elf file, so I am using this
>real vmlinux file.
Maybe there is a problem in your virtual prototype system (VM?).
Jan
--
-
To unsubscr
On Sat, 18 Aug 2007, Chris Wright wrote:
> >
> > Check the latest git head. Does it still break?
>
> Yeah, this is the latest git. The broken commit is Rusty's patch which,
> after Linus reverted the write-protected remap changes, is no longer
> necessary. AFAICT patching is writing garbage i
On Sun, Aug 12, 2007 at 10:54:45AM -0400, Mathieu Desnoyers wrote:
> the #endif /* CONFIG_SMP */ should cover the default condition, or it may
> cause
> bad parameter to be silently missed.
>
> Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
> CC: [EMAIL PROTECTED]
>
* Andi Kleen ([EMAIL PROTECTED]) wrote:
> > This patch breaks Xen booting.
>
> Check the latest git head. Does it still break?
Yeah, this is the latest git. The broken commit is Rusty's patch which,
after Linus reverted the write-protected remap changes, is no longer
necessary. AFAICT patchin
Brennan Ashton wrote:
On 8/18/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
On Aug 18 2007 12:08, Marty Leisner wrote:
In embedded system design, it may be useful to poweroff the disks (as opposed
to merely spinning them down). We want to leave the system running while
the disk is powered down
subscribe linux-kernel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
this vmlinux file is running on my software virtual prototype system.
and my software enviorment can only load elf file, so I am using this
real vmlinux file.
regards,
Yang
2007/8/18, Jan Engelhardt <[EMAIL PROTECTED]>:
>
> On Aug 18 2007 21:49, Xu Yang wrote:
> >
> >I tried as what you told me.
On Aug 18 2007 21:49, Xu Yang wrote:
>
>I tried as what you told me. and the vmlinux does contain debug
>information. but the start address of this vmlinux is 0xc0008000. when
>I tried to run this vmlinux, the program always exit at 0x80a0. I
>checked out that here is the place mmu is turned on.
>
Hi Jesper,
I tried as what you told me. and the vmlinux does contain debug
information. but the start address of this vmlinux is 0xc0008000. when
I tried to run this vmlinux, the program always exit at 0x80a0. I
checked out that here is the place mmu is turned on.
so I used objcopy --change-addres
Package: linux-image-2.6.22-1-amd64
Version: 2.6.22-3
Severity: grave
Justification: renders package unusable
hi all,
I encountered the same problem than
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg182088.html.
/var/log/dmesg.2.gz:
- = - = - = - = - = - = - = - = - = - = -
* Rafael J. Wysocki ([EMAIL PROTECTED]) wrote:
> On Sunday, 12 August 2007 01:43, Dr. David Alan Gilbert wrote:
> > * Pavel Machek ([EMAIL PROTECTED]) wrote:
> > > Hi!
> > >
> > > > > > Two things which I think would be nice to consider are:
> > > > > >1) Encryption - I'd actually prefer if my
Package: linux-image-2.6.22-1-amd64
Version: 2.6.22-3
Severity: grave
Justification: renders package unusable
hi all,
I encountered the same problem than
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg182088.html.
/var/log/dmesg.2.gz:
- = - = - = - = - = - = - = - = - = - = -
Am Freitag, 17. August 2007 schrieben Sie:
> On Fri, 17 Aug 2007, Andreas Jellinghaus [c] wrote:
> > I need some kernel event that has both DEVICE and MODALIAS set.
> > up to including kernel 2.6.21 this seems to come from
> > drivers/usb/core/driver.c if I read the code correctly, and then
> > it
On 8/18/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>
> On Aug 18 2007 12:08, Marty Leisner wrote:
> >
> >In embedded system design, it may be useful to poweroff the disks (as opposed
> >to merely spinning them down). We want to leave the system running while
> >the disk is powered down, and let
On Fri 17 Aug 2007 18:34, David Brownell pondered:
> On Friday 17 August 2007, Robin Getz wrote:
> > On Fri 17 Aug 2007 14:24, David Brownell pondered:
> > > Just for the record, this is an unusual way to use these calls.
> >
> > That is part of the natural evolution of the kernel isn't it - per
>
On 08/18, Neil Horman wrote:
>
> +static int proc_pid_limits(struct task_struct *task, char *buffer)
> +{
> + unsigned int i;
> + int count = 0;
> + unsigned long flags;
> + char *bufptr = buffer;
> +
> + struct rlimit rlim[RLIM_NLIMITS];
> +
> + read_lock(&tasklist_lock);
>
On Saturday 18 August 2007 19:22:18 Linus Torvalds wrote:
>
> Hmm. I think this is wrong.
>
> Why? Because the regular 32-bit x86 code does this all completely
> differently, and doesn't use dma_mask at all. Instead, it _only_ uses
> dev->coherent_dma_mask (which, considering the name of the f
Ok, I think I see your point. Thanks for the input. New patch attached which
adds the use of the sighand lock to the patch.
Currently, there exists no method for a process to query the resource
limits of another process. They can be inferred via some mechanisms but
they cannot be explicitly d
> The problem is that on x86-64 you are overriding memset()
I don't. You must be looking at old source
asm-x86_64/string.h 2.6.23rc3:
#define __HAVE_ARCH_MEMSET
void *memset(void *s, int c, size_t n);
I wanted to do the same on i386 too, but there were some minor obstacles.
The problem is th
On Sat, Aug 18, 2007 at 09:45:54AM -0700, Marc Perkel wrote:
> Linux isn't going to make progress when people try to
> figure out how to make something NOT work rather than
> to make something work. So if you are going to put
> effort into this then why not try to figure out how to
> get around t
On Thu, Aug 09, 2007 at 05:36:39PM +0100, Maciej W. Rozycki wrote:
> On Thu, 9 Aug 2007, Olaf Hering wrote:
>
> > include/linux/if_fddi.h is an exported header.
> > It uses __be16. Include linux/types.h to get this prototype.
>
> Please note that for userland it does not matter. With glibc you
Jiri Slaby wrote:
Randy Dunlap napsal(a):
On Sat, 18 Aug 2007 11:44:12 +0200 (CEST) Jiri Slaby wrote:
define global BIT macro
move all local BIT defines to the new globally define macro.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
include/linux/bitops.h |1 +
this latest project of cramming the full definition of each kernel
subsystem into the MAINTAINERS file has been bothering me, and i've
finally figured out why. it's because the MAINTAINERS file is being
asked to now be the source of reference information that just doesn't
match its name. it's
Now that we don't pre-allocate the new ->sighand, we can kill the first fast
path, it doesn't make sense any longer. At best, it can save one "list_empty()"
check but leads to the code duplication.
Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]>
--- t/fs/exec.c~4_FASTPATH 2007-08-18 19:10:5
de_thread() yields waiting for ->group_leader to be a zombie. This deadlocks
if an rt-prio execer shares the same cpu with ->group_leader. Change the code
to use ->group_exit_task/notify_count mechanics.
This patch certainly uglifies the code, perhaps someone can suggest something
better.
Signed-
de_thread() pre-allocates newsighand to make sure that exec() can't fail after
killing all sub-threads. Imho, this buys nothing, but complicates the code:
- this is (mostly) needed to handle CLONE_SIGHAND without CLONE_THREAD
tasks, this is very unlikely (if ever used) case
de_thread:
if (atomic_read(&oldsighand->count) <= 1)
BUG_ON(atomic_read(&sig->count) != 1);
This is not safe without the rmb() in between. The results of two correctly
ordered __exit_signal()->atomic_dec_and_test()'s could be seen out of order
on our CPU.
The same is true
There is no any reason to do recalc_sigpending() after changing ->sighand.
To begin with, recalc_sigpending() does not take ->sighand into account.
This means we don't need to take newsighand->siglock while changing sighands.
rcu_assign_pointer() provides a necessary barrier, and if another proces
Hmm. I think this is wrong.
Why? Because the regular 32-bit x86 code does this all completely
differently, and doesn't use dma_mask at all. Instead, it _only_ uses
dev->coherent_dma_mask (which, considering the name of the function,
would seem to make sense).
Considering that the oops comes
On Sat, Aug 18, 2007 at 04:45:31PM +0800, Fengguang Wu wrote:
> Matt,
>
> On Sat, Aug 18, 2007 at 01:40:42AM -0500, Matt Mackall wrote:
> > > - On memory pressure,
> > > - as VSZ goes up, RSS will be bounded by physical memory.
> > > So VSZ:RSS ratio actually goes up with memory pressure.
>
Randy Dunlap napsal(a):
> On Sat, 18 Aug 2007 11:44:12 +0200 (CEST) Jiri Slaby wrote:
>
>> define global BIT macro
>>
>> move all local BIT defines to the new globally define macro.
>>
>> Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
>>
>> ---
>>
>> include/linux/bitops.h |
On Sat, Aug 18, 2007 at 10:00:42AM -0700, Joe Perches wrote:
> On Sat, 2007-08-18 at 11:00 -0400, J. Bruce Fields wrote:
> > Also, some paths that are shared with the client:
> > +F: fs/lockd/
> > +F: fs/nfs_common/
> > +F: net/sunrpc/
> > +F: include/linux/lockd/
> > +F: include/linux/sunrpc/
>
>
On Sat, 2007-08-18 at 10:05 -0700, Randy Dunlap wrote:
> > + PLEASE include the appropriate maintainers and developers
> > + that have modified files touched by your patch by using the
> s/that/who/
> > + automated CC generator (scripts/get_maintainer.pl)
Right.
-
To unsubscribe from this l
On Sat, 18 Aug 2007 00:08:54 -0700 Joe Perches wrote:
> Added patterns to describe files maintained.
>
> Signed-off-by: Joe Perches <[EMAIL PROTECTED]>
>
>
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d3a0684..d7fe1c5 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -19,40 +19,44 @@ t
On Sat, 2007-08-18 at 11:00 -0400, J. Bruce Fields wrote:
> Also, some paths that are shared with the client:
> +F: fs/lockd/
> +F: fs/nfs_common/
> +F: net/sunrpc/
> +F: include/linux/lockd/
> +F: include/linux/sunrpc/
This is what I have now:
KERNEL NFSD
P: J. Bruce Fields
M:
--- Kyle Moffett <[EMAIL PROTECTED]> wrote:
> On Aug 17, 2007, at 15:01:48, Phillip Susi wrote:
> > [EMAIL PROTECTED] wrote:
> >> It will become even *more* of a "not that common"
> if the lock will
> >> block moves and ACL changes *across the
> filesystem* for
> >> potentially *minutes* at a
On Sat, 18 Aug 2007 11:44:12 +0200 (CEST) Jiri Slaby wrote:
> define global BIT macro
>
> move all local BIT defines to the new globally define macro.
>
> Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
>
> ---
>
> include/linux/bitops.h |1 +
> include/video/sstfb.h
Hi Joe,
> > Patch removed until there is a consensus on how to proceed with your
> > proposal.
>
> Hi Wim.
>
> I think that's wise.
>
> I've got all the changes that people have CC'd me.
> I expect it'll be an all or nothing sort of thing.
My opinion: the patch you sent me was just adding the
On Aug 18 2007 17:28, Chris Boot wrote:
>
> I will. This will probably be on Monday now, since the machine isn't
> accepting SysRq requests over the serial console. :-(
Ah yeah, stupid null-modem cables!
You can also trigger sysrq from /proc/sysrq-trigger (well, as long
as the system lives)
Måns Rullgård wrote:
Chris Boot <[EMAIL PROTECTED]> writes:
Måns Rullgård wrote:
Chris Boot <[EMAIL PROTECTED]> writes:
All,
I've got a box running RHEL5 and haven't been impressed by ext3
performance on it (running of a 1.5TB HP MSA20 using the cciss
driver). I compiled XFS
On Aug 18 2007 12:08, Marty Leisner wrote:
>
>In embedded system design, it may be useful to poweroff the disks (as opposed
>to merely spinning them down). We want to leave the system running while
>the disk is powered down, and let the disk powerup when it needs to be
>spun up.
That means you
Fix f_version type: should be u64 instead of long
There is a type inconsistency between struct inode i_version and struct file
f_version.
fs.h:
struct inode
u64 i_version;
and
struct file
unsigned long f_version;
Users do:
fs/ext3/dir.c:
if (filp->f_version
In embedded system design, it may be useful to poweroff the disks (as opposed
to merely spinning them down). We want to leave the system running while
the disk is powered down, and let the disk powerup when it needs to be
spun up.
While the "power off mechanism" would be platform dependent, is
* Fengguang Wu ([EMAIL PROTECTED]) wrote:
> Al Viro,
>
> Does this sounds like a good fix?
> ===
>
> seq_file version fixes
>
> - f_version is 'unsigned long', it's pointless to do more than that.
Hrm, this is weird...
fs.h:
struct inode
u64 i_version;
and
struct file
On Sat, Aug 18, 2007 at 05:32:05PM +0200, Stefan Richter wrote:
> These don't appear anywhere else in the kernel anymore.
>
> Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
> Cc: Bryan Wu <[EMAIL PROTECTED]>
> Cc: Yoshinori Sato <[EMAIL PROTECTED]>
> Cc: Greg Ungerer <[EMAIL PROTECTED]>
> Cc: P
Chris Boot <[EMAIL PROTECTED]> writes:
> Måns Rullgård wrote:
>> Chris Boot <[EMAIL PROTECTED]> writes:
>>
>>
>>> All,
>>>
>>> I've got a box running RHEL5 and haven't been impressed by ext3
>>> performance on it (running of a 1.5TB HP MSA20 using the cciss
>>> driver). I compiled XFS as a module
On Sat 18 Aug 2007 02:23, Sam Ravnborg pondered:
> > > What was preventing you from just using the x86_64 code here?
> >
> > Some was borrowed - but not much. since we don't support vga, or
> > 16550 UARTs (Blackfin has it's own on-chip UART), I don't think
> > this would work. Everyone impleme
These don't appear anywhere else in the kernel anymore.
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
Cc: Bryan Wu <[EMAIL PROTECTED]>
Cc: Yoshinori Sato <[EMAIL PROTECTED]>
Cc: Greg Ungerer <[EMAIL PROTECTED]>
Cc: Paul Mundt <[EMAIL PROTECTED]>
Cc: Miles Bader <[EMAIL PROTECTED]>
---
include
On 2007/08/16 , at 13:01, Karsten Keil wrote:
On Thu, Aug 16, 2007 at 01:22:04PM +0300, Ilpo Järvinen wrote:
...I guess those guys hunting for broken busyloops in the other
thread
could also benefit from similar searching commands introduced in this
thread... ...Ccing Satyam to caught the
On Sat, Aug 18, 2007 at 12:08:54AM -0700, Joe Perches wrote:
> KERNEL NFSD
> P: J. Bruce Fields
> M: [EMAIL PROTECTED]
> P: Neil Brown
> M: [EMAIL PROTECTED]
> L: [EMAIL PROTECTED]
> W: http://nfs.sourceforge.net/
> S: Supported
> +F: fs/nfsd/
> +F: include/linux/nfsd/
Al
On Sat, 18 Aug 2007 11:46:24 +0200
Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Saturday 18 August 2007 01:34:46 Stephen Hemminger wrote:
> > Optimize uses of memset with small constant offsets.
> > This will generate smaller code, and avoid the slow rep/string instructions.
> > Code copied from i38
Måns Rullgård wrote:
Chris Boot <[EMAIL PROTECTED]> writes:
All,
I've got a box running RHEL5 and haven't been impressed by ext3
performance on it (running of a 1.5TB HP MSA20 using the cciss
driver). I compiled XFS as a module and tried it out since I'm used to
using it on Debian, which ru
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.
>>
>>
>> Which
On Sat, 18 Aug 2007, Jan Engelhardt wrote:
> On Aug 18 2007 20:07, Satyam Sharma wrote:
> >On Fri, 17 Aug 2007, Geert Uytterhoeven wrote:
> >
> >> On Thu, 16 Aug 2007, NeilBrown wrote:
> >> [...]
> >> > dev_dbg(&dev->sbd.core,
> >> > "%s:%u: bio %u: %u s
On Sat, 18 Aug 2007, Segher Boessenkool wrote:
> > > GCC manual, section 6.1, "When
^^
> > > is a Volatile Object Accessed?" doesn't say anything of the
^^^
> > > kind.
^
> > True, "impleme
On Aug 18 2007 20:07, Satyam Sharma wrote:
>On Fri, 17 Aug 2007, Geert Uytterhoeven wrote:
>
>> On Thu, 16 Aug 2007, NeilBrown wrote:
>> [...]
>> >dev_dbg(&dev->sbd.core,
>> >"%s:%u: bio %u: %u segs %u sectors from %lu\n",
>> > - __func__, __LINE__,
Hi list,
I am facing a very strange issue about device probe order.
I have a piece of code to support network interface card for an embedded box.
It likes following:
...
static struct platform_device *custom_devices[] __initdata = {
&a_device,
&b_device,
&c_device,
On Fri, 17 Aug 2007, Geert Uytterhoeven wrote:
> On Thu, 16 Aug 2007, NeilBrown wrote:
> [...]
> > dev_dbg(&dev->sbd.core,
> > "%s:%u: bio %u: %u segs %u sectors from %lu\n",
> > - __func__, __LINE__, i, bio_segments(bio),
> > -
When 'Show debug info' is checked then a list of links
to dependant symbols is shown in info view right bottom pane.
Currently all links are in standard blue. With this patch
links to disabled symbols are shown in red instead.
This, together with 'Show all options', allows to quickly
check out wh
On Fri, 17 Aug 2007, Jeff Dike wrote:
> Style fixes in hostfs.
> Index: linux-2.6.22/fs/hostfs/hostfs_kern.c
> [...]
> @@ -6,22 +6,15 @@
> * 2003-02-10 Petr Baudis <[EMAIL PROTECTED]>
> */
>
> -#include
> #include
> #include
> -#include
> -#include
> +#include
> #include
> -#inc
--- Willy Tarreau <[EMAIL PROTECTED]> wrote:
> OK, in this trace, both controllers are on the same
> bus. The broken
> one has 'Capabilities: [100] Advanced Error
> Reporting' the other
> does not have, and the bridge to this bus has two
> more capabilities :
> 'Capabilities: [100] Virtual Channel
It seems unlikely, but access to self_id_cpu[0] could at least in theory
be deferred until after the loop over self_id_cpu[1..n] or even after
the subsequent reg_read. Enforce the desired order by a read barrier.
Also prevent the reg_read from being reordered relative to the for loop.
This isn't
Martin K. Petersen wrote:
>> "Stefan" == Stefan Richter <[EMAIL PROTECTED]> writes:
>
> Stefan> There were some similar reports involving that "status write
> Stefan> for unknown orb". I haven't found a way to reproduce it; I
> Stefan> noticed it only once in the logs here so far.
>
> I get
On Fri, 17 Aug 2007, Linus Torvalds wrote:
> On Sat, 18 Aug 2007, Satyam Sharma wrote:
> >
> > No code does (or would do, or should do):
> >
> > x.counter++;
> >
> > on an "atomic_t x;" anyway.
>
> That's just an example of a general problem.
>
> No, you don't use "x.counter++". But you
[ LOL, you _are_ shockingly petty! ]
On Sat, 18 Aug 2007, Segher Boessenkool wrote:
> > > The documentation simply doesn't say "+m" is allowed. The code to
> > > allow it was added for the benefit of people who do not read the
> > > documentation. Documentation for "+m" might get added later i
On 08/18, Neil Horman wrote:
>
> On Sat, Aug 18, 2007 at 02:22:28AM +0400, Oleg Nesterov wrote:
> > Neil Horman wrote:
> > >
> > > +static int proc_pid_limits(struct task_struct *task, char *buffer)
> > > +{
> > > + unsigned int i;
> > > + int count = 0;
> > > + char *bufptr = buffer;
> > > +
> >
1 - 100 of 136 matches
Mail list logo
