Hi!
> > I should take some sleep now, so I can't test the patch, but I don't
> > think it will help. If someone has PF_FREEZE set, he should be in
> > refrigerator.
>
> OK, so if that doesn't help, here's an alternate approach - this
> lets xfsbufd track when its entering the refrigerator(), so
Hi,
On Tuesday, 12 of April 2005 01:51, Pavel Machek wrote:
]--snip--[
> > Since the refrigerator() call is in place in the main xfsbufd loop,
> > I suspect we're hitting that second case here, where a low memory
> > situation is resulting in someone attempting to wakeup xfsbufd --
> > I'm not
his patch helped.
I can confirm, the 2nd patch worked and the 1st one didn't. (This is
against 2.6.12-rc2-mm1 with sched-x86-patch-name-is-way-too-long.patch
backed out. ;) )
-Barry K. Nathan <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&
Hi,
On Tuesday, 12 of April 2005 01:51, Pavel Machek wrote:
]--snip--[
Since the refrigerator() call is in place in the main xfsbufd loop,
I suspect we're hitting that second case here, where a low memory
situation is resulting in someone attempting to wakeup xfsbufd --
I'm not sure if
Hi!
I should take some sleep now, so I can't test the patch, but I don't
think it will help. If someone has PF_FREEZE set, he should be in
refrigerator.
OK, so if that doesn't help, here's an alternate approach - this
lets xfsbufd track when its entering the refrigerator(), so that
On Tue, Apr 12, 2005 at 01:51:10AM +0200, Pavel Machek wrote:
> I should take some sleep now, so I can't test the patch, but I don't
> think it will help. If someone has PF_FREEZE set, he should be in
> refrigerator.
OK, so if that doesn't help, here's an alternate approach - this
lets xfsbufd
Hi!
> > > > > No, XFS is my root filesystem. :( (Now that I think about it, would
> > > > > modularizing XFS and using an initrd be OK?)
> > > >
> > > > Yes, loading xfs from initrd should help. [At least it did during
> > > > suse9.3 testing.]
> > >
> > > Once I modularized xfs and switched to
On Mon, Apr 11, 2005 at 12:57:59PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > No, XFS is my root filesystem. :( (Now that I think about it, would
> > > > modularizing XFS and using an initrd be OK?)
> > >
> > > Yes, loading xfs from initrd should help. [At least it did during
> > > suse9.3
On Mon, 2005-04-11 at 12:45 +0200, Thomas Graf wrote:
> * Evgeniy Polyakov <[EMAIL PROTECTED]> 2005-04-11 09:22
> > On Sun, Apr 10, 2005 at 09:27:27PM +0200, Thomas Graf ([EMAIL PROTECTED])
> > wrote:
> > > + size = NLMSG_SPACE(sizeof(*msg) + msg->len);
> > > +
> > > + skb =
Hi!
> > > No, XFS is my root filesystem. :( (Now that I think about it, would
> > > modularizing XFS and using an initrd be OK?)
> >
> > Yes, loading xfs from initrd should help. [At least it did during
> > suse9.3 testing.]
>
> Once I modularized xfs and switched to using an initrd, the
* Evgeniy Polyakov <[EMAIL PROTECTED]> 2005-04-11 09:22
> On Sun, Apr 10, 2005 at 09:27:27PM +0200, Thomas Graf ([EMAIL PROTECTED])
> wrote:
> > + size = NLMSG_SPACE(sizeof(*msg) + msg->len);
> > +
> > + skb = alloc_skb(size, GFP_ATOMIC);
> > + if (!skb) {
> > +
Hi,
I am having problems while booting 2.6.12-rc2-mm1 on i386 with command line
maxcpus=1. Without this commandline, system boots fine otherwise it hangs.
Serial output is pasted below.
If maxcpus=1 is given along with acpi=off then system boots fine. I am not sure
where the problem
Barry K. Nathan wrote:
> On Sun, Apr 10, 2005 at 11:27:47PM +0200, Pavel Machek wrote:
>> Can you try without XFS?
>
> No, XFS is my root filesystem. :( (Now that I think about it, would
> modularizing XFS and using an initrd be OK?)
Yes, although it is not totally trivial.
> I'll see if I can
Barry K. Nathan wrote:
On Sun, Apr 10, 2005 at 11:27:47PM +0200, Pavel Machek wrote:
Can you try without XFS?
No, XFS is my root filesystem. :( (Now that I think about it, would
modularizing XFS and using an initrd be OK?)
Yes, although it is not totally trivial.
I'll see if I can
Hi,
I am having problems while booting 2.6.12-rc2-mm1 on i386 with command line
maxcpus=1. Without this commandline, system boots fine otherwise it hangs.
Serial output is pasted below.
If maxcpus=1 is given along with acpi=off then system boots fine. I am not sure
where the problem
* Evgeniy Polyakov [EMAIL PROTECTED] 2005-04-11 09:22
On Sun, Apr 10, 2005 at 09:27:27PM +0200, Thomas Graf ([EMAIL PROTECTED])
wrote:
+ size = NLMSG_SPACE(sizeof(*msg) + msg-len);
+
+ skb = alloc_skb(size, GFP_ATOMIC);
+ if (!skb) {
+ printk(KERN_ERR
Hi!
No, XFS is my root filesystem. :( (Now that I think about it, would
modularizing XFS and using an initrd be OK?)
Yes, loading xfs from initrd should help. [At least it did during
suse9.3 testing.]
Once I modularized xfs and switched to using an initrd, the problem
On Mon, 2005-04-11 at 12:45 +0200, Thomas Graf wrote:
* Evgeniy Polyakov [EMAIL PROTECTED] 2005-04-11 09:22
On Sun, Apr 10, 2005 at 09:27:27PM +0200, Thomas Graf ([EMAIL PROTECTED])
wrote:
+ size = NLMSG_SPACE(sizeof(*msg) + msg-len);
+
+ skb = alloc_skb(size,
On Mon, Apr 11, 2005 at 12:57:59PM +0200, Pavel Machek wrote:
Hi!
No, XFS is my root filesystem. :( (Now that I think about it, would
modularizing XFS and using an initrd be OK?)
Yes, loading xfs from initrd should help. [At least it did during
suse9.3 testing.]
Once I
Hi!
No, XFS is my root filesystem. :( (Now that I think about it, would
modularizing XFS and using an initrd be OK?)
Yes, loading xfs from initrd should help. [At least it did during
suse9.3 testing.]
Once I modularized xfs and switched to using an initrd, the
On Tue, Apr 12, 2005 at 01:51:10AM +0200, Pavel Machek wrote:
I should take some sleep now, so I can't test the patch, but I don't
think it will help. If someone has PF_FREEZE set, he should be in
refrigerator.
OK, so if that doesn't help, here's an alternate approach - this
lets xfsbufd track
On Sun, Apr 10, 2005 at 09:27:27PM +0200, Thomas Graf ([EMAIL PROTECTED]) wrote:
> * jamal <[EMAIL PROTECTED]> 2005-04-10 10:39
> > Please crosspost on netdev - you should know that by now;->
> >
> > I actually disagreee with Herbert on this. Theres definetely good
> > need to have a more usable
On Mon, Apr 11, 2005 at 01:00:53AM +0200, Pavel Machek wrote:
> > No, XFS is my root filesystem. :( (Now that I think about it, would
> > modularizing XFS and using an initrd be OK?)
>
> Yes, loading xfs from initrd should help. [At least it did during
> suse9.3 testing.]
Once I modularized xfs
Hi!
> > Can you try without XFS?
>
> No, XFS is my root filesystem. :( (Now that I think about it, would
> modularizing XFS and using an initrd be OK?)
Yes, loading xfs from initrd should help. [At least it did during
suse9.3 testing.]
> I'll see if I can reproduce this on one of my test
On Sun, Apr 10, 2005 at 11:27:47PM +0200, Pavel Machek wrote:
> Can you try without XFS?
No, XFS is my root filesystem. :( (Now that I think about it, would
modularizing XFS and using an initrd be OK?)
I'll see if I can reproduce this on one of my test boxes. I'll *try* to
get to it later today,
Hi!
> (Sorry I took so long to respond. I was busy with tons of stuff
> offline...)
>
> On Fri, Apr 08, 2005 at 12:33:27PM +0200, Pavel Machek wrote:
> > Do you have XFS compiled in, by chance?
>
> Yes.
Can you try without XFS?
I do not why it interferes, but I've seen that before on suse
(Sorry I took so long to respond. I was busy with tons of stuff
offline...)
On Fri, Apr 08, 2005 at 12:33:27PM +0200, Pavel Machek wrote:
> Do you have XFS compiled in, by chance?
Yes.
> You are not actually resuming from initrd, right?
That is correct.
-Barry K. Nathan <[EMAIL PROTECTED]>
-
* jamal <[EMAIL PROTECTED]> 2005-04-10 10:39
> Please crosspost on netdev - you should know that by now;->
>
> I actually disagreee with Herbert on this. Theres definetely good
> need to have a more usable messaging system that rides on top of
> netlink. It is not that netlink cant be extended (I
On Sun, 2005-04-10 at 10:56, James Morris wrote:
> On 10 Apr 2005, jamal wrote:
>
> > Thats what the original motivation for konnector was. To make it easy
> > for joe dumbass.
>
> Who you really want writing kernel code :-)
Ok, let me take that back then ;->
The value is in allowing people who
On 10 Apr 2005, jamal wrote:
> Thats what the original motivation for konnector was. To make it easy
> for joe dumbass.
Who you really want writing kernel code :-)
- James
--
James Morris
<[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Evgeniy,
Please crosspost on netdev - you should know that by now;->
I actually disagreee with Herbert on this. Theres definetely good
need to have a more usable messaging system that rides on top of
netlink. It is not that netlink cant be extended (I actually think thats
a separate topic) - its
On Sun, 10 Apr 2005 14:10:05 +0200
Thomas Graf <[EMAIL PROTECTED]> wrote:
> * Evgeniy Polyakov <[EMAIL PROTECTED]> 2005-04-10 15:37
> > --- ./net/netlink/af_netlink.c.orig 2005-04-10 15:46:48.0 +0400
> > +++ ./net/netlink/af_netlink.c 2005-04-10 15:47:04.0 +0400
> > @@ -747,7
* Evgeniy Polyakov <[EMAIL PROTECTED]> 2005-04-10 15:37
> --- ./net/netlink/af_netlink.c.orig 2005-04-10 15:46:48.0 +0400
> +++ ./net/netlink/af_netlink.c 2005-04-10 15:47:04.0 +0400
> @@ -747,7 +747,7 @@
> if (p->exclude_sk == sk)
> goto out;
>
> -
On Sun, 10 Apr 2005 15:37:57 +0400
Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> The second one is a huge monster that can not be used in embedded
> systems, calling userspace process from inside the kernel is
> now very flexible way.
is NOT very flexible way...
Evgeniy Polyakov
Only
On Sun, 10 Apr 2005 13:08:44 +0200
Kay Sievers <[EMAIL PROTECTED]> wrote:
> On Sun, 2005-04-10 at 14:32 +0400, Evgeniy Polyakov wrote:
> > On Sun, 10 Apr 2005 19:52:54 +1000
> > Herbert Xu <[EMAIL PROTECTED]> wrote:
> > > Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> > > >
> > > > User should
On Sun, 2005-04-10 at 14:32 +0400, Evgeniy Polyakov wrote:
> On Sun, 10 Apr 2005 19:52:54 +1000
> Herbert Xu <[EMAIL PROTECTED]> wrote:
> > Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> > >
> > > User should not know about low-level transport -
> > > it is like socket layer - write only data
On Sun, 10 Apr 2005 19:52:54 +1000
Herbert Xu <[EMAIL PROTECTED]> wrote:
> Please add netdev to the CC list since this discussion pertains to
> the networking subsystem.
>
> Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> >
> > User should not know about low-level transport -
> > it is like
Please add netdev to the CC list since this discussion pertains to
the networking subsystem.
Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
>
> User should not know about low-level transport -
> it is like socket layer - write only data and do not care about
> how it will be delivered.
The
Please add netdev to the CC list since this discussion pertains to
the networking subsystem.
Evgeniy Polyakov [EMAIL PROTECTED] wrote:
User should not know about low-level transport -
it is like socket layer - write only data and do not care about
how it will be delivered.
The delineation
On Sun, 10 Apr 2005 19:52:54 +1000
Herbert Xu [EMAIL PROTECTED] wrote:
Please add netdev to the CC list since this discussion pertains to
the networking subsystem.
Evgeniy Polyakov [EMAIL PROTECTED] wrote:
User should not know about low-level transport -
it is like socket layer -
On Sun, 2005-04-10 at 14:32 +0400, Evgeniy Polyakov wrote:
On Sun, 10 Apr 2005 19:52:54 +1000
Herbert Xu [EMAIL PROTECTED] wrote:
Evgeniy Polyakov [EMAIL PROTECTED] wrote:
User should not know about low-level transport -
it is like socket layer - write only data and do not care
On Sun, 10 Apr 2005 13:08:44 +0200
Kay Sievers [EMAIL PROTECTED] wrote:
On Sun, 2005-04-10 at 14:32 +0400, Evgeniy Polyakov wrote:
On Sun, 10 Apr 2005 19:52:54 +1000
Herbert Xu [EMAIL PROTECTED] wrote:
Evgeniy Polyakov [EMAIL PROTECTED] wrote:
User should not know about low-level
On Sun, 10 Apr 2005 15:37:57 +0400
Evgeniy Polyakov [EMAIL PROTECTED] wrote:
The second one is a huge monster that can not be used in embedded
systems, calling userspace process from inside the kernel is
now very flexible way.
is NOT very flexible way...
Evgeniy Polyakov
Only
* Evgeniy Polyakov [EMAIL PROTECTED] 2005-04-10 15:37
--- ./net/netlink/af_netlink.c.orig 2005-04-10 15:46:48.0 +0400
+++ ./net/netlink/af_netlink.c 2005-04-10 15:47:04.0 +0400
@@ -747,7 +747,7 @@
if (p-exclude_sk == sk)
goto out;
- if
On Sun, 10 Apr 2005 14:10:05 +0200
Thomas Graf [EMAIL PROTECTED] wrote:
* Evgeniy Polyakov [EMAIL PROTECTED] 2005-04-10 15:37
--- ./net/netlink/af_netlink.c.orig 2005-04-10 15:46:48.0 +0400
+++ ./net/netlink/af_netlink.c 2005-04-10 15:47:04.0 +0400
@@ -747,7 +747,7 @@
Evgeniy,
Please crosspost on netdev - you should know that by now;-
I actually disagreee with Herbert on this. Theres definetely good
need to have a more usable messaging system that rides on top of
netlink. It is not that netlink cant be extended (I actually think thats
a separate topic) - its
On 10 Apr 2005, jamal wrote:
Thats what the original motivation for konnector was. To make it easy
for joe dumbass.
Who you really want writing kernel code :-)
- James
--
James Morris
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
On Sun, 2005-04-10 at 10:56, James Morris wrote:
On 10 Apr 2005, jamal wrote:
Thats what the original motivation for konnector was. To make it easy
for joe dumbass.
Who you really want writing kernel code :-)
Ok, let me take that back then ;-
The value is in allowing people who are
* jamal [EMAIL PROTECTED] 2005-04-10 10:39
Please crosspost on netdev - you should know that by now;-
I actually disagreee with Herbert on this. Theres definetely good
need to have a more usable messaging system that rides on top of
netlink. It is not that netlink cant be extended (I
(Sorry I took so long to respond. I was busy with tons of stuff
offline...)
On Fri, Apr 08, 2005 at 12:33:27PM +0200, Pavel Machek wrote:
Do you have XFS compiled in, by chance?
Yes.
You are not actually resuming from initrd, right?
That is correct.
-Barry K. Nathan [EMAIL PROTECTED]
-
To
Hi!
(Sorry I took so long to respond. I was busy with tons of stuff
offline...)
On Fri, Apr 08, 2005 at 12:33:27PM +0200, Pavel Machek wrote:
Do you have XFS compiled in, by chance?
Yes.
Can you try without XFS?
I do not why it interferes, but I've seen that before on suse
kernels...
On Sun, Apr 10, 2005 at 11:27:47PM +0200, Pavel Machek wrote:
Can you try without XFS?
No, XFS is my root filesystem. :( (Now that I think about it, would
modularizing XFS and using an initrd be OK?)
I'll see if I can reproduce this on one of my test boxes. I'll *try* to
get to it later today,
Hi!
Can you try without XFS?
No, XFS is my root filesystem. :( (Now that I think about it, would
modularizing XFS and using an initrd be OK?)
Yes, loading xfs from initrd should help. [At least it did during
suse9.3 testing.]
I'll see if I can reproduce this on one of my test boxes. I'll
On Mon, Apr 11, 2005 at 01:00:53AM +0200, Pavel Machek wrote:
No, XFS is my root filesystem. :( (Now that I think about it, would
modularizing XFS and using an initrd be OK?)
Yes, loading xfs from initrd should help. [At least it did during
suse9.3 testing.]
Once I modularized xfs and
On Sun, Apr 10, 2005 at 09:27:27PM +0200, Thomas Graf ([EMAIL PROTECTED]) wrote:
* jamal [EMAIL PROTECTED] 2005-04-10 10:39
Please crosspost on netdev - you should know that by now;-
I actually disagreee with Herbert on this. Theres definetely good
need to have a more usable messaging
On Thu, Apr 07, 2005 at 11:02:22PM -0700, David S. Miller wrote:
> On Fri, 08 Apr 2005 09:19:39 +0400
> Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
>
> > > I know, the same thing holds for most architectures, including i386.
> > > However, this is not an issue for uni-processor kernels anywhere
Hi!
> > > Ok, I've narrowed the problem down to one patch. In 2.6.11-mm3, the
> > > problem goes away if I remove this patch:
> > > swsusp-enable-resume-from-initrd.patch
> >
> > That really helps, thanks.
>
> You're welcome.
>
> > The patch looks fairly innocent. I'll give up on this and cc
On Fri, 2005-04-08 at 01:55 -0400, James Morris wrote:
> On Fri, 8 Apr 2005, Evgeniy Polyakov wrote:
>
> > > > Sure, but seems I need to ask again: What is the exact reason not to
> > > > implement
> > > > the muticast message multiplexing/subscription part of the connector as
> > > > a
> > > >
On Fri, 2005-04-08 at 09:19 +0400, Evgeniy Polyakov wrote:
> On Fri, 2005-04-08 at 15:08 +1000, Herbert Xu wrote:
> > On Fri, Apr 08, 2005 at 09:11:56AM +0400, Evgeniy Polyakov wrote:
> > >
> > > > Yes but what will go wrong on uni-processor MIPS when you don't do the
> > > > sync in
On Fri, 08 Apr 2005 09:19:39 +0400
Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> > I know, the same thing holds for most architectures, including i386.
> > However, this is not an issue for uni-processor kernels anywhere else,
> > so what's so special about MIPS?
>
> Does i386 or ppc has cached
On Fri, 08 Apr 2005 09:19:39 +0400
Evgeniy Polyakov [EMAIL PROTECTED] wrote:
I know, the same thing holds for most architectures, including i386.
However, this is not an issue for uni-processor kernels anywhere else,
so what's so special about MIPS?
Does i386 or ppc has cached and
On Fri, 2005-04-08 at 09:19 +0400, Evgeniy Polyakov wrote:
On Fri, 2005-04-08 at 15:08 +1000, Herbert Xu wrote:
On Fri, Apr 08, 2005 at 09:11:56AM +0400, Evgeniy Polyakov wrote:
Yes but what will go wrong on uni-processor MIPS when you don't do the
sync in atomic_sub_return?
On Fri, 2005-04-08 at 01:55 -0400, James Morris wrote:
On Fri, 8 Apr 2005, Evgeniy Polyakov wrote:
Sure, but seems I need to ask again: What is the exact reason not to
implement
the muticast message multiplexing/subscription part of the connector as
a
generic part of
Hi!
Ok, I've narrowed the problem down to one patch. In 2.6.11-mm3, the
problem goes away if I remove this patch:
swsusp-enable-resume-from-initrd.patch
That really helps, thanks.
You're welcome.
The patch looks fairly innocent. I'll give up on this and cc the
developers.
On Thu, Apr 07, 2005 at 11:02:22PM -0700, David S. Miller wrote:
On Fri, 08 Apr 2005 09:19:39 +0400
Evgeniy Polyakov [EMAIL PROTECTED] wrote:
I know, the same thing holds for most architectures, including i386.
However, this is not an issue for uni-processor kernels anywhere else,
so
On Fri, 8 Apr 2005, Evgeniy Polyakov wrote:
> > > Sure, but seems I need to ask again: What is the exact reason not to
> > > implement
> > > the muticast message multiplexing/subscription part of the connector as a
> > > generic part of netlink? That would be nice to have and useful for other
>
On Fri, 2005-04-08 at 15:08 +1000, Herbert Xu wrote:
> On Fri, Apr 08, 2005 at 09:11:56AM +0400, Evgeniy Polyakov wrote:
> >
> > > Yes but what will go wrong on uni-processor MIPS when you don't do the
> > > sync in atomic_sub_return?
> >
> > Sync synchornizes cached mamory access,
> > without it
On Fri, Apr 08, 2005 at 09:11:56AM +0400, Evgeniy Polyakov wrote:
>
> > Yes but what will go wrong on uni-processor MIPS when you don't do the
> > sync in atomic_sub_return?
>
> Sync synchornizes cached mamory access,
> without it new value may be stored only into cache,
> but not into memory.
I
On Fri, 2005-04-08 at 14:53 +1000, Herbert Xu wrote:
> On Fri, Apr 08, 2005 at 08:55:27AM +0400, Evgeniy Polyakov wrote:
> >
> > > > Unfortunately not, that sync is required exactly for return value store.
> > >
> > > On UP?
> >
> > Yes, some quotes:
>
> Yes but what will go wrong on
On Fri, 8 Apr 2005 14:53:02 +1000
Herbert Xu <[EMAIL PROTECTED]> wrote:
> Yes but what will go wrong on uni-processor MIPS when you don't do the
> sync in atomic_sub_return?
Indeed. I see nothing in those quotes which indicate that the
SYNC is needed on uniprocessor. It's only saying things
On Fri, Apr 08, 2005 at 08:55:27AM +0400, Evgeniy Polyakov wrote:
>
> > > Unfortunately not, that sync is required exactly for return value store.
> >
> > On UP?
>
> Yes, some quotes:
Yes but what will go wrong on uni-processor MIPS when you don't do the
sync in atomic_sub_return?
Cheers,
--
On Fri, 2005-04-08 at 14:17 +1000, Herbert Xu wrote:
> On Fri, Apr 08, 2005 at 08:21:28AM +0400, Evgeniy Polyakov wrote:
> >
> > > > On UP do not.
> > >
> > > Shouldn't we should be fixing the MIPS implementation of
> > > atomic_sub_return to not do the sync on UP then?
> >
> > Unfortunately
On Fri, 08 Apr 2005 07:52:34 +0400
Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> sparc64 has 32->64 conversation on exit.
It's extremely cheap, the conversion instruction
pairs with the retl instruction so it's essentially
free.
Talking about an arithmetic instruction over is complete
nonsense
On Fri, 8 Apr 2005 14:17:24 +1000
Herbert Xu <[EMAIL PROTECTED]> wrote:
> On UP?
I think the barrier can be eliminated on MIPS on UP.
-
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, Apr 08, 2005 at 08:21:28AM +0400, Evgeniy Polyakov wrote:
>
> > > On UP do not.
> >
> > Shouldn't we should be fixing the MIPS implementation of
> > atomic_sub_return to not do the sync on UP then?
>
> Unfortunately not, that sync is required exactly for return value store.
On UP?
--
On Fri, 2005-04-08 at 14:02 +1000, Herbert Xu wrote:
> On Fri, Apr 08, 2005 at 08:02:49AM +0400, Evgeniy Polyakov wrote:
> >
> > > > mips has additional sync.
> > >
> > > But atomic_dec + 2 barries is going to do the sync as well, no?
> >
> > On UP do not.
>
> Shouldn't we should be fixing the
On Fri, Apr 08, 2005 at 08:02:49AM +0400, Evgeniy Polyakov wrote:
>
> > > mips has additional sync.
> >
> > But atomic_dec + 2 barries is going to do the sync as well, no?
>
> On UP do not.
Shouldn't we should be fixing the MIPS implementation of
atomic_sub_return to not do the sync on UP then?
On Fri, 2005-04-08 at 13:50 +1000, Herbert Xu wrote:
> On Fri, Apr 08, 2005 at 07:52:34AM +0400, Evgeniy Polyakov wrote:
> > On Fri, 2005-04-08 at 13:32 +1000, Herbert Xu wrote:
> > > On Fri, Apr 08, 2005 at 07:33:58AM +0400, Evgeniy Polyakov wrote:
> > > > On Fri, 2005-04-08 at 12:59 +1000,
On Fri, Apr 08, 2005 at 07:52:34AM +0400, Evgeniy Polyakov wrote:
> On Fri, 2005-04-08 at 13:32 +1000, Herbert Xu wrote:
> > On Fri, Apr 08, 2005 at 07:33:58AM +0400, Evgeniy Polyakov wrote:
> > > On Fri, 2005-04-08 at 12:59 +1000, Herbert Xu wrote:
> > > > Evgeniy Polyakov <[EMAIL PROTECTED]>
On Fri, 2005-04-08 at 13:32 +1000, Herbert Xu wrote:
> On Fri, Apr 08, 2005 at 07:33:58AM +0400, Evgeniy Polyakov wrote:
> > On Fri, 2005-04-08 at 12:59 +1000, Herbert Xu wrote:
> > > Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> > > >
> > > > atomic_dec_and_test() is more expensive than 2
On Thu, 2005-04-07 at 11:47 -0400, James Morris wrote:
> On Thu, 7 Apr 2005, Kay Sievers wrote:
>
> > Sure, but seems I need to ask again: What is the exact reason not to
> > implement
> > the muticast message multiplexing/subscription part of the connector as a
> > generic part of netlink? That
On Fri, Apr 08, 2005 at 07:33:58AM +0400, Evgeniy Polyakov wrote:
> On Fri, 2005-04-08 at 12:59 +1000, Herbert Xu wrote:
> > Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> > >
> > > atomic_dec_and_test() is more expensive than 2 barriers + atomic_dec(),
> > > but in case of connector I think the
On Fri, 2005-04-08 at 12:59 +1000, Herbert Xu wrote:
> Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> >
> > atomic_dec_and_test() is more expensive than 2 barriers + atomic_dec(),
> > but in case of connector I think the price is not so high.
>
> Can you list the platforms on which this is true?
Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
>
> atomic_dec_and_test() is more expensive than 2 barriers + atomic_dec(),
> but in case of connector I think the price is not so high.
Can you list the platforms on which this is true?
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email:
On Thu, 2005-04-07 at 18:08 -0700, Siddha, Suresh B wrote:
> On Thu, Apr 07, 2005 at 03:11:12AM +1000, Nick Piggin wrote:
> > Using the attached patch, a puny dual PIII-650 with ~400MB RAM swapped
> > itself to death after 2 infinite loop tasks had been pinned to one
> > of the CPUs. See how
On Thu, Apr 07, 2005 at 03:11:12AM +1000, Nick Piggin wrote:
> Using the attached patch, a puny dual PIII-650 with ~400MB RAM swapped
> itself to death after 2 infinite loop tasks had been pinned to one
> of the CPUs. See how you go.
Its goes well beyond the initial 7000 number I mentioned.
On Thu, Apr 07, 2005 at 01:58:45AM -0700, Andrew Morton wrote:
> > I'm having problems with 1394 in 2.6.12-rc2-mm1. When I connect my
> > Apple iSight camera, it is not detected; repeated
> > connections/disconnections don't help. When I tried to rmmod all the
> > ap
Hi Andrew,
Le Tuesday 05 April 2005 09:45, Andrew Morton a écrit :
> Brice Goglin <[EMAIL PROTECTED]> wrote:
> > Andrew Morton a écrit :
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.
> > >12-rc2/2.6.12-rc2-mm1/
> >
> > H
On Thu, 7 Apr 2005, Kay Sievers wrote:
> Sure, but seems I need to ask again: What is the exact reason not to implement
> the muticast message multiplexing/subscription part of the connector as a
> generic part of netlink? That would be nice to have and useful for other
> subsystems too as an
On Thu, 2005-04-07 at 16:23 +0200, Kay Sievers wrote:
> Sure, but seems I need to ask again: What is the exact reason not to implement
> the muticast message multiplexing/subscription part of the connector as a
> generic part of netlink? That would be nice to have and useful for other
>
On Thu, Apr 07, 2005 at 03:24:34PM +0400, Evgeniy Polyakov wrote:
> On Thu, 2005-04-07 at 12:41 +0200, Kay Sievers wrote:
> > On Thu, 2005-04-07 at 13:52 +0400, Evgeniy Polyakov wrote:
> > > On Thu, 2005-04-07 at 10:12 +0100, Ian Campbell wrote:
> > > > On Thu, 2005-04-07 at 12:13 +0400, Evgeniy
On Thu, 2005-04-07 at 12:41 +0200, Kay Sievers wrote:
> On Thu, 2005-04-07 at 13:52 +0400, Evgeniy Polyakov wrote:
> > On Thu, 2005-04-07 at 10:12 +0100, Ian Campbell wrote:
> > > On Thu, 2005-04-07 at 12:13 +0400, Evgeniy Polyakov wrote:
> > > > The main idea was to simplify userspace control and
On Thu, 2005-04-07 at 13:52 +0400, Evgeniy Polyakov wrote:
> On Thu, 2005-04-07 at 10:12 +0100, Ian Campbell wrote:
> > On Thu, 2005-04-07 at 12:13 +0400, Evgeniy Polyakov wrote:
> > > The main idea was to simplify userspace control and notification
> > > system - so people did not waste it's time
On Thu, 2005-04-07 at 01:32 -0700, Andrew Morton wrote:
> Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > Plus, I'm still quite unsettled about the whole object lifecycle
> > > management, refcounting and locking in there. The fact that the code is
> > > littered with peculiar
On Thu, 2005-04-07 at 10:12 +0100, Ian Campbell wrote:
> On Thu, 2005-04-07 at 12:13 +0400, Evgeniy Polyakov wrote:
> > The main idea was to simplify userspace control and notification
> > system - so people did not waste it's time learning how skb's are
> > allocated
> > and processed, how socket
On Thu, 2005-04-07 at 12:13 +0400, Evgeniy Polyakov wrote:
> The main idea was to simplify userspace control and notification
> system - so people did not waste it's time learning how skb's are
> allocated
> and processed, how socket layer is designed and what all those
> netlink_* and NLMSG* mean
Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
>
> I'm having problems with 1394 in 2.6.12-rc2-mm1. When I connect my
> Apple iSight camera, it is not detected; repeated
> connections/disconnections don't help. When I tried to rmmod all the
> appropriate modules (rm
I'm having problems with 1394 in 2.6.12-rc2-mm1. When I connect my
Apple iSight camera, it is not detected; repeated
connections/disconnections don't help. When I tried to rmmod all the
appropriate modules (rmmod video1394 raw1394 ohci1394 ieee1394), the
rmmod command hung. Alt-Sysreq-t shows
Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
>
> >
> > Plus, I'm still quite unsettled about the whole object lifecycle
> > management, refcounting and locking in there. The fact that the code is
> > littered with peculiar barriers says "something weird is happening here",
> > and it remains
; > > Hello,
> > > >
> > > > I don't see the connector directory in the 2.6.12-rc2-mm1 tree. So it
> > > > seems that you removed the connector?
> > >
> > > Greg dropped it for some reason. I think that's best because it needed a
> > &g
1 - 100 of 313 matches
Mail list logo
