7;t know if a fix is going on somewhere
or if the bug has fallen in a black hole.
(In the original mail, I've proposed a patch as a quick fix, but I don't know if
it can be considered as a definitive correction or not)
Thanks,
P.
Andrew Morton wrote:
> On Mon, 4 Feb 2008 16:29:
Andi Kleen wrote:
> [EMAIL PROTECTED] writes:
>
>> This is a resend of the first part of the patchset sent 2 weeks
>> ago. This is the part about the IPC which (again) proposes to consolidate
>> some part of the existing code.
>>
>> It does not change the behavior of the existing code,
On Feb 13, 2008 9:07 PM, Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 12, 2008 at 05:13:41PM +0100, [EMAIL PROTECTED] wrote:
> > Trivial patch which adds some small locking functions and makes use of them
> > to factorize some part of the code and to make it cleaner.
>
> What's wrong wi
these same pieces of code
into one common function called ipcctl_pre_down().
It simplifies a little these xxxctl_down() functions and increases a little
the maintainability.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
Acked-by: Serge Hallyn <[EMAIL PROTECTED]>
---
ipc/m
From: Pierre Peiffer <[EMAIL PROTECTED]>
The IPC_SET command performs the same permission setting for all IPCs.
This patch introduces a common ipc_update_perm() function to update these
permissions and makes use of it for all IPCs.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]&
From: Pierre Peiffer <[EMAIL PROTECTED]>
All IPCs make use of an intermetiate *_setbuf structure to handle the
IPC_SET command. This is not really needed and, moreover, it complicates
a little bit the code.
This patch get rid of the use of it and uses directly the semid64_ds/
msgi
From: Pierre Peiffer <[EMAIL PROTECTED]>
semctl_down() takes one unused parameter: semnum.
This patch proposes to get rid of it.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
Acked-by: Serge Hallyn <[EMAIL PROTECTED]>
---
ipc/sem.c |6 +++---
1 file changed, 3 insertio
From: Pierre Peiffer <[EMAIL PROTECTED]>
Currently, sys_msgctl is not easy to read.
This patch tries to improve that by introducing the msgctl_down function
to handle all commands requiring the rwmutex to be taken in write mode
(ie IPC_SET and IPC_RMID for now). It is the equivalent funct
From: Pierre Peiffer <[EMAIL PROTECTED]>
semctl_down is called with the rwmutex (the one which protects the
list of ipcs) taken in write mode.
This patch moves this rwmutex taken in write-mode inside semctl_down.
This has the advantages of reducing a little bit the window during
whic
From: Pierre Peiffer <[EMAIL PROTECTED]>
Currently, the way the different commands are handled in sys_shmctl
introduces some duplicated code.
This patch introduces the shmctl_down function to handle all the commands
requiring the rwmutex to be taken in write mode (ie IPC_SET and IPC_RMID
f
From: Pierre Peiffer <[EMAIL PROTECTED]>
Trivial patch which adds some small locking functions and makes use of them
to factorize some part of the code and to make it cleaner.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
Acked-by: Serge Hallyn <[EMAIL PROTECTED]>
---
vmlinux
textdata bss dec hex filename
1902917 175820 122880 2201617 219811 obj/vmlinux
--
Pierre Peiffer
--
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.kerne
Hi,
By continuing to consolidate a little the IPC code, each id can be built
directly in ipc_addid() instead of having it built from each callers of
ipc_addid()
And I also remove shm_addid() in order to have, as much as possible, the
same code for shm/sem/msg.
Signed-off-by: Pierre Peiffer
es (sigh... just
>
> Agreed.
>
>> think of clone() nightmare to add a new argument);
>
> Yes, and then there will need to be the clone_with_pid() extension on
> top of that.
>
>> second, the change
>> is incremental: first code the mechanism to set the f
this error with
the following patch.
As NS8390p_init() does the same thing than NS8390_init(), I suppose that this
is the right fix ?
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
drivers/net/ne.c |6 +++---
1 file changed, 3 insertions(+), 3 del
Pavel Machek wrote:
> Hi!
>
>> * Patches 9 to 15 propose to add some functionalities, and thus are
>> submitted here for RFC, about both the interest and their implementation.
>> These functionalities are:
>> - Two new control-commands:
>> . IPC_SETID: to change an IPC's id.
>> . I
Serge E. Hallyn wrote:
> Quoting Pierre Peiffer ([EMAIL PROTECTED]):
>>
>> Serge E. Hallyn wrote:
>>> Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
>>>> From: Pierre Peiffer <[EMAIL PROTECTED]>
>>>>
>>>> In order to modif
of concern as well.
Honestly, I don't think this really a concern at all. I mean: I've never seen
"this allows non-GPL binary and thus, this is bad" as an argument to reject a
functionality, but I may be wrong, and thus, it can be discussed as well.
I think th
Nadia Derbey wrote:
> [EMAIL PROTECTED] wrote:
>> From: Pierre Peiffer <[EMAIL PROTECTED]>
>>
>> semctl_down() takes one unused parameter: semnum.
>> This patch proposes to get rid of it.
>>
>> Signed-off-by: Pierre Peiffer <[EMAIL PROTECT
Serge E. Hallyn wrote:
> Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
>> From: Pierre Peiffer <[EMAIL PROTECTED]>
>>
>> Today, the sem_undo_list is freed when the last task using it exits.
>> There is no mechanism in place, that allows a safe concurrent ac
Serge E. Hallyn wrote:
> Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
>> From: Pierre Peiffer <[EMAIL PROTECTED]>
>>
>> In order to modify the semundo-list of a task from procfs, we must be able to
>> work on any target task.
>> But all the exis
Hi again,
Thinking more about this, I think I must clarify why I choose this way.
In fact, the idea of these patches is to provide the missing user APIs (or
extend the existing ones) that allow to set or update _all_ properties of all
IPCs, as needed in the case of the checkpoint/restart o
necessarily a problem, as we
will probably restart an application in an empty "container"/"namespace"; Thus
we can create all needed IPCs in an empty IPC namespace like this:
1. create first IPC
2. change its ID
3. create the second IPC
4. change its ID
5. etc..
But yes,
From: Pierre Peiffer <[EMAIL PROTECTED]>
This patch adds the write operation to the semundo file.
This write operation allows root to add or update the semundo list and
their values for a given process.
The user must provide some lines, each containing the semaphores ID
followed
From: Pierre Peiffer <[EMAIL PROTECTED]>
In order to modify the semundo-list of a task from procfs, we must be able to
work on any target task.
But all the existing code playing with the semundo-list, currently works
only on the 'current' task, and does not allow to specify any ta
From: Pierre Peiffer <[EMAIL PROTECTED]>
This patch adds a new procfs interface to display the per-process semundo
data.
A new per-PID file is added, named "semundo".
It contains one line per semaphore IPC where there is something to undo for
this process.
Then, each line co
From: Pierre Peiffer <[EMAIL PROTECTED]>
Today, the sem_undo_list is freed when the last task using it exits.
There is no mechanism in place, that allows a safe concurrent access to
the sem_undo_list of a target task and protects efficiently against a
task-exit.
That is okay for now as we
From: Pierre Peiffer <[EMAIL PROTECTED]>
This patch adds a new IPC_SETALL command to the System V IPCs set of commands,
which allows to change all the settings of an IPC
It works exactly the same way as the IPC_SET command, except that it
additionally changes all the times and the pids
From: Pierre Peiffer <[EMAIL PROTECTED]>
This patch adds a new IPC_SETID command to the System V IPCs set of commands,
which allows to change the ID of an existing IPC.
This command can be used through the semctl/shmctl/msgctl API, with the new
ID passed as the third argument for msgc
From: Pierre Peiffer <[EMAIL PROTECTED]>
This patch provides three new API to change the ID of an existing
System V IPCs.
These APIs are:
long msg_chid(struct ipc_namespace *ns, int id, int newid);
long sem_chid(struct ipc_namespace *ns, int id, int newid);
long sh
these same pieces of code
into one common function called ipcctl_pre_down().
It simplifies a little these xxxctl_down() functions and increases a little
the maintainability.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
Acked-by: Serge Hallyn <[EMAIL PROTECTED]>
---
ipc/m
From: Pierre Peiffer <[EMAIL PROTECTED]>
The IPC_SET command performs the same permission setting for all IPCs.
This patch introduces a common ipc_update_perm() function to update these
permissions and makes use of it for all IPCs.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]&
From: Pierre Peiffer <[EMAIL PROTECTED]>
All IPCs make use of an intermetiate *_setbuf structure to handle the
IPC_SET command. This is not really needed and, moreover, it complicate
a little bit the code.
This patch get rid of the use of it and uses directly the semid64_ds/
msgi
From: Pierre Peiffer <[EMAIL PROTECTED]>
semctl_down is called with the rwmutex (the one which protects the
list of ipcs) taken in write mode.
This patch moves this rwmutex taken in write-mode inside semctl_down.
This has the advantages of reducing a little bit the window during
whic
From: Pierre Peiffer <[EMAIL PROTECTED]>
semctl_down() takes one unused parameter: semnum.
This patch proposes to get rid of it.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
Acked-by: Serge Hallyn <[EMAIL PROTECTED]>
---
ipc/sem.c |6 +++---
1 file changed, 3 insertio
From: Pierre Peiffer <[EMAIL PROTECTED]>
Currently, sys_msgctl is not easy to read.
This patch tries to improve that by introducing the msgctl_down function
to handle all commands requiring the rwmutex to be taken in write mode
(ie IPC_SET and IPC_RMID for now). It is the equivalent funct
From: Pierre Peiffer <[EMAIL PROTECTED]>
Currently, the way the different commands are handled in sys_shmctl
introduces some duplicated code.
This patch introduces the shmctl_down function to handle all the commands
requiring the rwmutex to be taken in write mode (ie IPC_SET and IPC_RMID
f
From: Pierre Peiffer <[EMAIL PROTECTED]>
Trivial patch which adds some small locking functions and makes use of them
to factorize some part of code and makes it cleaner.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
Acked-by: Serge Hallyn <[EMAIL PROTECTED]>
---
Hi,
Here is a patchset about the IPC, which proposes to consolidate some
part of the existing code and to add some functionalities.
* Patches 1 to 8 don't change the existing behavior, but propose to rewrite
some parts of the existing code. In fact, the three kinds of IPC (semaphores,
mes
Andrew Morton wrote:
> Doing this in a piecemeal through-a-pinhole fashion won't work very well
> and is a bit risky.
Yes, agree, that's also my feeling.
--
Pierre Peiffer
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
the actual message follows immediately */
};
is acceptable ?
Otherwise, either a cast can be added or this patch can be dropped...
Thanks,
--
Pierre Peiffer
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More maj
-fix-comment-for-nonexistent-variable.patch
> +ext-use-ext_get_group_desc.patch
> +ext-remove-unused-argument-for-ext_find_goal.patch
> +ext-cleanup-ext_bg_num_gdb.patch
>
> ext2/3/4 cleanups
>
> +per-zone-and-reclaim-enhancements-for-memory-controller-take-3-modifies-vmsca
The file exit.c contains one useless extern declaration of sem_exit().
Moreover, it refers to nothing.
This trivial patch removes it.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
kernel/exit.c |2 --
1 file changed, 2 deletions(-)
Index: b/kernel/
From: Pierre Peiffer <[EMAIL PROTECTED]>
These both commands (SEM_STAT and IPC_STAT) are rather doing the same things
(only the meaning of the id given as input and the return value differ).
However, for the semaphores, they are handled in two different places
(two different functions).
introducing a common function,
free_ipcs(),
that do the job. The specific routine to call on each individual ipcs is passed
as
parameter. For this, these ipc-specific 'free' routines are reworked to take a
generic 'struct ipc_perm' as parameter.
Signed-off-by: Pierre Peiff
Andrew,
Following this discussion http://lkml.org/lkml/2007/11/27/54, I
resend the three patches that I've sent last friday to let you have all of
them in the right order.
Thanks,
--
Pierre Peiffer
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
From: Pierre Peiffer <[EMAIL PROTECTED]>
Each ipc_namespace contains a table of 3 pointers to struct ipc_ids (3 for
msg, sem and shm, structure used to store each ipcs)
These pointers are dynamically allocated for each icp_namespace as the
ipc_namespace itself (for the init namespace, th
Andrew Morton wrote:
> On Mon, 26 Nov 2007 22:44:38 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
>
>> On Fri, 23 Nov 2007 17:52:50 +0100 Pierre Peiffer <[EMAIL PROTECTED]> wrote:
>>
>>> sem_exit_ns(), msg_exit_ns() and shm_exit_ns() are all called when a
introducing a common function,
free_ipcs(),
that do the job. The specific routine to call on each individual ipcs is passed
as
parameter. For this, these ipc-specific 'free' routines are reworked to take a
generic 'struct ipc_perm' as parameter.
Signed-off-by: Pierre Peiff
handling these both
commands in the same place in semctl_nolock(). It also removes one
unused parameter for this function.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
ipc/sem.c | 38 --
1 file changed, 16 insertions(+), 22 deletions(-)
In
Pavel Emelyanov wrote:
> Well I think you're right. The structure gains 50% in size... Really too
> much to fight for performance in IPC :)
>
> Thanks for checking this thing.
>
> You may put my Acked-by in the original patch.
>
Cool. Thanks !
P.
> Thanks,
> P
wrote:
> Pierre Peiffer wrote:
>> Hi,
>>
>> Thanks for reviewing this !
>>
>> Pavel Emelyanov wrote:
>>> Pavel Emelyanov wrote:
>>>> Cedric Le Goater wrote:
>>>>> Pierre Peiffer wrote:
>>> [snip]
>>>
>>
Hi,
Thanks for reviewing this !
Pavel Emelyanov wrote:
> Pavel Emelyanov wrote:
>> Cedric Le Goater wrote:
>>> Pierre Peiffer wrote:
>
> [snip]
>
>>> Pavel, what do you think of it ?
>> Looks sane, good catch, Pierre.
>>
>> But
e ipc_ids separately.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
include/linux/ipc_namespace.h | 13 +++--
ipc/msg.c | 26 --
ipc/namespace.c | 25 -
ipc/sem.c
Andrew Morton wrote:
> On Tue, 30 Oct 2007 17:13:50 +0100
> Pierre Peiffer <[EMAIL PROTECTED]> wrote:
>
>> ida_pre_get() and idr_pre_get() currently return 0 in case of error, and 1
>> in case of success, what is not the conventional way to handle error cases.
>>
reported instead of ENOMEM. This avoids to the callers to make any assumption
about the cause of the error.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
arch/powerpc/mm/mmu_context_64.c |5 +++--
block/bsg.c|4 +---
drivers/ch
eck will be done several times (in all sub-callers...),
what is not
very funny/optimal...
That's why I send this as RFC.
Comments or other proposals are welcome, but there are some corrections to do
anyway.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
ipc/msg.c |
d solution is simple and correct. But it has the drawback
of adding one more check ('if' statement) in the chain: we do a first check in
ipc_lock(), now in xxx_lock() and then one later in the caller of xxx_lock()
That's why I send this as RFC, may be another approach could be conside
d.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
ipc/msg.c |4 ++--
ipc/sem.c |4 ++--
ipc/shm.c |5 +++--
ipc/util.c | 16 +++-
4 files changed, 18 insertions(+), 11 deletions(-)
In
in 2.6.24 if Nadia's patches are included.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
ipc/msg.c |4 ++--
ipc/sem.c |4 ++--
ipc/shm.c |5 +++--
ipc/util.c | 35 +--
4 files changed, 28 insertions(+), 20 deletions(-)
Index:
From: Pierre Peiffer <[EMAIL PROTECTED]>
Some comments about sem_undo_list seem wrong.
About the comment above unlock_semundo:
"... If task2 now exits before task1 releases the lock (by calling
unlock_semundo()), then task1 will never call spin_unlock(). ..."
This is just wrong,
it.
These patches give you the possibility of changing this ID once the IPC is
created.
--
Pierre Peiffer
-
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/
From: Pierre Peiffer <[EMAIL PROTECTED]>
This patch adds a new IPC_SETID command to the System V IPCs set of commands,
which allows to change the ID of an existing IPC.
This command can be used through the semctl/shmctl/msgctl API, with the new
ID passed as the third argument for msgc
From: Pierre Peiffer <[EMAIL PROTECTED]>
This patch provides three new API for changing the ID of an existing
System V IPCs.
These APIs are:
long msg_mvid(struct ipc_namespace *ns, int id, int newid);
long sem_mvid(struct ipc_namespace *ns, int id, int newid);
Hi,
As I'm seeing some discussion/interest about IPC, I would like to
propose these patches, which provide an easy way to change the ID of an exiting
IPC.
This work is done around the checkpoint/restart of applications. In the case of
the IPCs, we need (among others) this functionality.
Andrew Morton a écrit :
>
> yup, thanks, the maps2 patches in -mm already accidentally fixed this so I
> haven't
> bothered merging it as a standalone thing.
>
Ok, good.
Thanks,
--
Pierre
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [
From: Pierre Peiffer <[EMAIL PROTECTED]>
This is a trivial patch that removes some duplicated declarations of
extern variables.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
fs/proc/internal.h |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --g
From: Pierre Peiffer <[EMAIL PROTECTED]>
These extern variables are declared twice, so it removes one of the declaration.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
fs/proc/internal.h |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/fs/proc/
Thomas Gleixner wrote :
Patch d0aa7a70bf03b9de9e995ab272293be1f7937822 titled
"futex_requeue_pi optimization"
introduced user space visible changes to the futex syscall.
The patch is non-functional and there is no way to fix it proper before
the 2.6.22 release.
The breakage report ( http:/
Eric Dumazet a écrit :
Hi Andrew
Not sure if you prefer to wait Pierre work on futex64, so just in case, I
prepared this patch.
Update on this take6 :
- Rebased on linux-2.6.21-rc7-mm2 , since futex64 were droped from mm
Pierre, I can resubmit another patch on top on your next patch, so ple
u use
continuous values a simple jump table can be used and no conditionals.
Smaller and faster.
Something like that may be...
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
--
Pierre
---
include/asm-ia64/futex.h|8 -
include/asm-powerpc/futex.h |6 -
include/asm-s
will be done with 64bit futexes, I can't really maintain
it. So I'll let you take/modify/adapt this patch following your needs.
Thanks,
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
--
Pierre
---
include/asm-ia64/futex.h|8 -
include/asm-powerpc/futex.h |6 -
Hi,
Your fix looks correct but the compile-time option
CONFIG_PAGE_GROUP_BY_MOBILITY was removed in a patch I sent to Andrew
two days ago. It went into mm-commits last night so this problem should
no longer exist.
Ah ok, fine. Just forget it in this case :)
Thanks,
--
Pierre
-
To unsubscr
Hi,
This is a fix against the patch
do-not-group-pages-by-mobility-type-on-low-memory-systems.patch (include in -mm
tree):
The error "page_group_by_mobility_disabled undefinied" occured if
CONFIG_PAGE_GROUP_BY_MOBILITY is not set.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECT
safe side we should enforce it in get_futex_key(). I agree with
you : If we want to maximize performance, we could say : The check
*must* be done by the caller.
Well we _control_ the API, so let's make it as clean and performant as
possible
from the start.
--
Pierre Peiffer
-
To u
This is a fix for a bug introduced by the patch
make-futex_wait-use-an-hrtimer-for-timeout.patch : the timeout value
is not passed anymore to futex_lock_pi.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
kernel/futex.c|8 ++--
kernel/futex_compat.c |4 +++-
2
off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
include/linux/futex.h |3 +
kernel/futex.c| 85 --
kernel/futex_compat.c | 17 --
3 files changed, 51 insertions(+), 54 deletions(-)
Index: b/ke
the glibc in pthread_broadcast, when
using "normal" mutexes. With futex_requeue_pi, it can be used with PRIO_INHERIT
mutexes too.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
include/linux/futex.h |9
kernel/futex.c
x64 for
now).
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
include/asm-x86_64/futex.h | 113 ++
include/asm-x86_64/unistd.h |4
include/linux/futex.h |9 -
include/linux/syscalls.h|3
kernel/futex.c
Hi Andrew,
This is a re-send of a series of patches concerning futexes (here
after is a short description).
I have reworked the patches to take into account the last changes
about futex, and this series should apply cleanly on -mm tree (the changes
mostly affect patch 2 "futex_wait
be
woken last, in FIFO order (RT-threads are woken first, in priority order).
Signed-off-by: Sebastien Dugue <[EMAIL PROTECTED]>
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
kernel/futex.c | 78 +++--
1 file changed, 4
Peter Zijlstra a écrit :
Unfortunately not, nonlinear vmas don't have a linear relation between
address and offset. What you would need to do is do a linear walk of the
page tables. But even that might not suffice if nonlinear vmas may form
a non-injective, surjective mapping.
/me checks..
Hm
Peter Zijlstra a écrit :
+static void *get_futex_address(union futex_key *key)
+{
+ void *uaddr;
+
+ if (key->both.offset & 1) {
+ /* shared mapping */
+ uaddr = (void*)((key->shared.pgoff << PAGE_SHIFT)
+ + key->shared.offset
used with PRIO_INHERIT
mutexes too.
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
include/linux/futex.h |8
kernel/futex.c | 557 +++-
kernel/futex_compat.c |3
kernel/rtmutex.c| 41 ---
kernel/rtmutex_commo
now).
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
include/asm-x86_64/futex.h | 113
include/asm-x86_64/unistd.h |4
include/linux/futex.h |7 -
include/linux/syscalls.h|3
kernel/futex.c
Hi Andrew,
This is a re-send of a series of patches concerning futexes (here after
is a short description)
Could you consider them for inclusion in -mm tree ?
All of them have already been discussed in January and have already
been included in -rt for a while. I think t
be
woken last, in FIFO order (RT-threads are woken first, in priority order).
Signed-off-by: Sébastien Dugué <[EMAIL PROTECTED]>
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
kernel/futex.c | 78 +++--
1 file changed, 4
}
if (op == FUTEX_REQUEUE || op == FUTEX_CMP_REQUEUE)
val2 = (int) (unsigned long) utime;
- return do_futex(uaddr, op, val, timeout, uaddr2, val2, val3);
+ return do_futex(uaddr, op, val, tp, uaddr2, val2, val3);
}
--
--
Pierre Peiffer
-
To unsubscribe from this li
Thomas Gleixner a écrit :
It is HRTIMER_MODE_xx in mainline as of 2.6.21-rc1. -rt kernels are
always a bit ahead of time. :)
Great !
Thanks.
--
Pierre
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info a
Hi,
Supposing I have an external kernel module which I would like to compile against
both original kernel and -rt kernel, what is the proper/most elegant way to know
which kernel I'm compiling with ?
I've only found the EXTRAVERSION define, am I missing a better way ?
In fact, I'm facing the
lowing patch: futex_lock_pi is also
involved.
---
futex.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
---
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
Index: linux-2.6/kernel/futex.c
===
--- li
| 247 ++--
kernel/futex_compat.c |3
kernel/sys_ni.c |1
7 files changed, 299 insertions(+), 77 deletions(-)
---
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
Index: linux-2.6/include/as
deletions(-)
---
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
Index: linux-2.6/include/linux/futex.h
===
--- linux-2.6.orig/include/linux/futex.h2007-01-17 09:44:42.0
+0100
+++ linux-2.6/include/linux/
/futex_compat.c | 11 +
3 files changed, 41 insertions(+), 30 deletions(-)
---
Signed-off-by: Sébastien Dugué <[EMAIL PROTECTED]>
Signed-off-by: Pierre Peiffer <[EMAIL PROTECTED]>
---
Index: linux-2.6/kernel/futex.c
=
them to be
woken last, in FIFO order (RT-threads are woken first, in priority order).
---
futex.c | 78
1 file changed, 49 insertions(+), 29 deletions(-)
---
Signed-off-by: Sébastien Dugué <[EMAIL PROTECTED]>
Signed-off-by:
Hi,
Today, there are several functionalities or improvements about futexes
included
in -rt kernel tree, which, I think, it make sense to have in mainline.
Among them, there are:
* futex use prio list : allows RT-threads to be woken in priority order
instead of FIFO order.
* fute
Ingo Molnar a écrit :
* Ulrich Drepper <[EMAIL PROTECTED]> wrote:
what do you mean by that - which is this same resource?
From what has been said here before, all futexes are stored in the
same list or hash table or whatever it was. I want to see how that
code behaves if many separate proces
Hi,
Ingo Molnar a écrit :
yeah. As an alternative, it might be a good idea to pthread-ify
hackbench.c - that should replicate the Volano workload pretty
accurately. I've attached hackbench.c. (it's process based right now, so
it wont trigger contended futex ops)
Ok, thanks. I've adapted your
Andrew Morton a écrit :
> OK. Unfortunately patches 2-4 don't apply without #1 present and the fix
> is not immediately obvious, so we'll need a respin+retest, please.
Ok, I'll provide updated patches for -mm ASAP.
On Thu, 11 Jan 2007 09:47:28 -0800
Ulrich Drepper <[EMAIL PROTECTED]> wrote:
Daniel Walker a écrit :
On Tue, 2007-01-09 at 17:16 +0100, Pierre Peiffer wrote:
@@ -1358,7 +1366,7 @@ static int futex_unlock_pi(u32 __user *u
struct futex_hash_bucket *hb;
struct futex_q *this, *next;
u32 uval;
- struct list_head *head;
+ struct plist_head
1 - 100 of 115 matches
Mail list logo
