Re: [take28-resend_2->0 0/8] kevent: Generic event handling mechanism.

2006-12-18 Thread Ulrich Drepper
It would help if one could actually get hold of the changes. Neither at home nor on my gmail account did I get them all. The gmane also only has 5 of the 9 mails or so. Your archive only has sources from a couple of versions back. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St

Re: [take28-resend_2-0 0/8] kevent: Generic event handling mechanism.

2006-12-18 Thread Ulrich Drepper
It would help if one could actually get hold of the changes. Neither at home nor on my gmail account did I get them all. The gmane also only has 5 of the 9 mails or so. Your archive only has sources from a couple of versions back. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St

Re: [take28-resend_2-0 0/8] kevent: Generic event handling mechanism.

2006-12-18 Thread Ulrich Drepper
Evgeniy Polyakov wrote: I've uploaded the latest changes to the homepage. Thanks. But could you now update the patch so that it can be compiled with the current upstream kernel? At least linux/kevent.h has problems because of file-st accesses. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444

Re: Question: removal of syscall macros?

2006-12-13 Thread Ulrich Drepper
On 12/13/06, Teunis Peters <[EMAIL PROTECTED]> wrote: Now that syscall macros have been pulled from the -mm tree, what method is recommended to use syscalls? glibc forever had a syscall() function for just that purpose. It was never a good idea to use the macros since they didn't work in PIC.

Re: Question: removal of syscall macros?

2006-12-13 Thread Ulrich Drepper
On 12/13/06, Teunis Peters [EMAIL PROTECTED] wrote: Now that syscall macros have been pulled from the -mm tree, what method is recommended to use syscalls? glibc forever had a syscall() function for just that purpose. It was never a good idea to use the macros since they didn't work in PIC. -

Re: Linux should define ENOTSUP

2006-12-07 Thread Ulrich Drepper
On 12/7/06, Andreas Schwab <[EMAIL PROTECTED]> wrote: The quoted sentence is not shaded as an XSI extension, thus it is part of POSIX-1:2001. Perhaps I didn't make myself clear. The change I pointed at was accepted to the interpretations track which means that if we would create a Technical

Re: Linux should define ENOTSUP

2006-12-07 Thread Ulrich Drepper
On 12/7/06, Andreas Schwab [EMAIL PROTECTED] wrote: The quoted sentence is not shaded as an XSI extension, thus it is part of POSIX-1:2001. Perhaps I didn't make myself clear. The change I pointed at was accepted to the interpretations track which means that if we would create a Technical

Re: Linux should define ENOTSUP

2006-12-06 Thread Ulrich Drepper
On 12/6/06, H. Peter Anvin <[EMAIL PROTECTED]> wrote: I'm quite aware of that, but I still think Sun has more resources to get their particular viewpoint through the committee -- it's just a matter of resources at hand. I myself had to largely drop out due to other pressures, for example. But

Re: Linux should define ENOTSUP

2006-12-06 Thread Ulrich Drepper
On 12/6/06, H. Peter Anvin <[EMAIL PROTECTED]> wrote: That's largely already the case, mostly because there is unfortunately still a fair bit of rubber-stamping Solaris going on. Don't say that, Peter. I'm working on the committee now for many years and got most changes I (and those telling

Re: Linux should define ENOTSUP

2006-12-06 Thread Ulrich Drepper
On 12/6/06, H. Peter Anvin [EMAIL PROTECTED] wrote: That's largely already the case, mostly because there is unfortunately still a fair bit of rubber-stamping Solaris going on. Don't say that, Peter. I'm working on the committee now for many years and got most changes I (and those telling me

Re: Linux should define ENOTSUP

2006-12-06 Thread Ulrich Drepper
On 12/6/06, H. Peter Anvin [EMAIL PROTECTED] wrote: I'm quite aware of that, but I still think Sun has more resources to get their particular viewpoint through the committee -- it's just a matter of resources at hand. I myself had to largely drop out due to other pressures, for example. But

Re: [take25 1/6] kevent: Description.

2006-11-27 Thread Ulrich Drepper
Evgeniy Polyakov wrote: It _IS_ how previous interface worked. EXACTLY! No, the old interface committed everything not only up to a given index. This is the huge difference which makes or breaks it. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA

Re: [take25 1/6] kevent: Description.

2006-11-27 Thread Ulrich Drepper
have probably noticed, there was such an interface already, and I changed it. So, this will be the last change of the interface. You think it should not be exported - fine, it will not be. Thanks. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - To unsubscribe from

Re: [take25 1/6] kevent: Description.

2006-11-27 Thread Ulrich Drepper
much more complicated than adding a simple index comparison before going to sleep. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More maj

Re: [take24 0/6] kevent: Generic event handling mechanism.

2006-11-27 Thread Ulrich Drepper
licate functionality. If there are performance problems with the POSIX timer implementation (and I have yet to see indications) it should be fixed instead of worked around. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - To unsubscribe from this list: send the line "

Re: Kevent POSIX timers support.

2006-11-27 Thread Ulrich Drepper
be passed to userland in one or two int fields, I don't really care. When reporting the event to the user code we cannot just point into the ring buffer anyway. So while copying the data we can rewrite it if necessary. I see no need to complicate the code more than it already is. -- ➧ Ulrich

Re: [take24 0/6] kevent: Generic event handling mechanism.

2006-11-27 Thread Ulrich Drepper
'd need to use indirect notification via >> signal or pipe or something like that. This is still something which is wanted. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the b

Re: Kevent POSIX timers support.

2006-11-27 Thread Ulrich Drepper
is sufficient and it should be passed up to the user in the ptr member of struct ukevent. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majo

Re: Kevent POSIX timers support.

2006-11-27 Thread Ulrich Drepper
is sufficient and it should be passed up to the user in the ptr member of struct ukevent. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info

Re: [take24 0/6] kevent: Generic event handling mechanism.

2006-11-27 Thread Ulrich Drepper
or pipe or something like that. This is still something which is wanted. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - 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

Re: Kevent POSIX timers support.

2006-11-27 Thread Ulrich Drepper
be passed to userland in one or two int fields, I don't really care. When reporting the event to the user code we cannot just point into the ring buffer anyway. So while copying the data we can rewrite it if necessary. I see no need to complicate the code more than it already is. -- ➧ Ulrich

Re: [take24 0/6] kevent: Generic event handling mechanism.

2006-11-27 Thread Ulrich Drepper
. If there are performance problems with the POSIX timer implementation (and I have yet to see indications) it should be fixed instead of worked around. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body

Re: [take25 1/6] kevent: Description.

2006-11-27 Thread Ulrich Drepper
complicated than adding a simple index comparison before going to sleep. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - 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

Re: [take25 1/6] kevent: Description.

2006-11-27 Thread Ulrich Drepper
have probably noticed, there was such an interface already, and I changed it. So, this will be the last change of the interface. You think it should not be exported - fine, it will not be. Thanks. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - To unsubscribe from

Re: [take25 1/6] kevent: Description.

2006-11-27 Thread Ulrich Drepper
Evgeniy Polyakov wrote: It _IS_ how previous interface worked. EXACTLY! No, the old interface committed everything not only up to a given index. This is the huge difference which makes or breaks it. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA

Re: [take24 0/6] kevent: Generic event handling mechanism.

2006-11-19 Thread Ulrich Drepper
lly when coupled with asynchronous filling of ring buffer (i.e., without a syscal). Let's solve problem in order of theirs appearance - what do you think about above interface for ring buffer? Looks better, yes. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - To

Re: [take24 0/6] kevent: Generic event handling mechanism.

2006-11-19 Thread Ulrich Drepper
with asynchronous filling of ring buffer (i.e., without a syscal). Let's solve problem in order of theirs appearance - what do you think about above interface for ring buffer? Looks better, yes. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - To unsubscribe from

Re: Add pselect, ppoll system calls.

2005-08-24 Thread Ulrich Drepper
. while (1) { if (!got_signal) pselect() if (got_signal) { handle signal got_signal = 0; } } ... } -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ signature.asc Description: OpenPGP digital signature

Re: Add pselect, ppoll system calls.

2005-08-24 Thread Ulrich Drepper
) { if (!got_signal) pselect() if (got_signal) { handle signal got_signal = 0; } } ... } -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ signature.asc Description: OpenPGP digital signature

Re: mremap() use is racy

2005-08-23 Thread Ulrich Drepper
) since this makes it clear what should happen but I can live with using the too-large mapping. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ signature.asc Description: OpenPGP digital signature

Re: mremap() use is racy

2005-08-23 Thread Ulrich Drepper
it is implemented today. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ signature.asc Description: OpenPGP digital signature

mremap() use is racy

2005-08-23 Thread Ulrich Drepper
, anonymous mappings which have no access permissions (i.e., PROT_NONE with MAP_PRIVATE and MAP_ANON). One explicitly has to allocate such blocks, they don't appear naturally. And the program in any case knows about the address space layout. So, how about adding MREMAP_MAPOVERNONE or so? -- ➧ Ulrich

mremap() use is racy

2005-08-23 Thread Ulrich Drepper
, anonymous mappings which have no access permissions (i.e., PROT_NONE with MAP_PRIVATE and MAP_ANON). One explicitly has to allocate such blocks, they don't appear naturally. And the program in any case knows about the address space layout. So, how about adding MREMAP_MAPOVERNONE or so? -- ➧ Ulrich

Re: mremap() use is racy

2005-08-23 Thread Ulrich Drepper
. Just accept here that moving is not an option. If remap cannot be used then a complete new mmap() with adjusted length is needed. That is unnecessarily expensive. It is the reason why there is mremap(). But mremap() with MREMAP_MAYMOVE is unreliable as it is implemented today. -- ➧ Ulrich

Re: mremap() use is racy

2005-08-23 Thread Ulrich Drepper
it clear what should happen but I can live with using the too-large mapping. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ signature.asc Description: OpenPGP digital signature

Re: [PATCH 2.6.13-rc6 1/2] New Syscall: get rlimits of any process (update)

2005-08-22 Thread Ulrich Drepper
On 8/18/05, Alan Cox <[EMAIL PROTECTED]> wrote: > Perhaps those application authors should provide a management interface > to do so within the soft limit range at least. Its not clear to me that > growing the fd array on a process is even safe. Some programs do size > arrays at startup after

Re: [PATCH 2.6.13-rc6 1/2] New Syscall: get rlimits of any process (update)

2005-08-22 Thread Ulrich Drepper
On 8/18/05, Alan Cox [EMAIL PROTECTED] wrote: Perhaps those application authors should provide a management interface to do so within the soft limit range at least. Its not clear to me that growing the fd array on a process is even safe. Some programs do size arrays at startup after querying

Re: pselect() modifying timeout

2005-08-05 Thread Ulrich Drepper
t from select. The userlevel code will take care of the difference. The kernel code is good as proposed. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ signature.asc Description: OpenPGP digital signature

Re: pselect() modifying timeout

2005-08-05 Thread Ulrich Drepper
select. The userlevel code will take care of the difference. The kernel code is good as proposed. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ signature.asc Description: OpenPGP digital signature

Re: Fw: sigwait() breaks when straced

2005-08-01 Thread Ulrich Drepper
On 8/1/05, Jesper Juhl <[EMAIL PROTECTED]> wrote: > I'm not quite sure you are right Ulrich. Given this little bit from > SUSv3 about SA_RESTART in the page describing sigaction ( > http://www.opengroup.org/onlinepubs/009695399/functions/sigaction.html > ) : It's not an official SA_RESTART since

Re: Fw: sigwait() breaks when straced

2005-08-01 Thread Ulrich Drepper
On 7/31/05, Roland McGrath <[EMAIL PROTECTED]> wrote: > However, there is in fact no bug here. The test program is just wrong. > sigwait returns zero or an error number, as POSIX specifies. No question, no error is detected incorrectly. But sigwait is not a function specified with an EINTR

Re: Fw: sigwait() breaks when straced

2005-08-01 Thread Ulrich Drepper
On 7/31/05, Roland McGrath [EMAIL PROTECTED] wrote: However, there is in fact no bug here. The test program is just wrong. sigwait returns zero or an error number, as POSIX specifies. No question, no error is detected incorrectly. But sigwait is not a function specified with an EINTR error

Re: Fw: sigwait() breaks when straced

2005-08-01 Thread Ulrich Drepper
On 8/1/05, Jesper Juhl [EMAIL PROTECTED] wrote: I'm not quite sure you are right Ulrich. Given this little bit from SUSv3 about SA_RESTART in the page describing sigaction ( http://www.opengroup.org/onlinepubs/009695399/functions/sigaction.html ) : It's not an official SA_RESTART since the

Re: sigwait() breaks when straced

2005-07-31 Thread Ulrich Drepper
On 7/30/05, Sanjoy Mahajan <[EMAIL PROTECTED]> wrote: > so the return value should not be 4 (or the docs are not right). This return value simply indicated EINTR (sigwait does not set errno, read the docs). The kernel simply doesn't restart the function in case of a signal. It should do this,

Re: sigwait() breaks when straced

2005-07-31 Thread Ulrich Drepper
On 7/30/05, Sanjoy Mahajan [EMAIL PROTECTED] wrote: so the return value should not be 4 (or the docs are not right). This return value simply indicated EINTR (sigwait does not set errno, read the docs). The kernel simply doesn't restart the function in case of a signal. It should do this,

Re: sigwait() and 2.6

2005-02-15 Thread Ulrich Drepper
On Tue, 15 Feb 2005 13:58:28 +0100, Yves Crespin <[EMAIL PROTECTED]> wrote: >ThreadUnblockSignal(); >signo = WaitSignal(); >ThreadBlockSignal(); You expect this to work? Just read the POSIX spec or even the man pages. All signals sigwait() waits for must be blocked

Re: sigwait() and 2.6

2005-02-15 Thread Ulrich Drepper
On Tue, 15 Feb 2005 13:58:28 +0100, Yves Crespin [EMAIL PROTECTED] wrote: ThreadUnblockSignal(); signo = WaitSignal(); ThreadBlockSignal(); You expect this to work? Just read the POSIX spec or even the man pages. All signals sigwait() waits for must be blocked before the

Re: close-exec flag not working in 2.6.9?

2005-01-31 Thread Ulrich Drepper
On Sun, 30 Jan 2005 23:56:07 -0800, Ben Greear <[EMAIL PROTECTED]> wrote: >flags = fcntl(s, F_GETFL); >flags |= (FD_CLOEXEC); >if (fcntl(s, F_SETFL, flags) < 0) { These have to be F_GETFD and F_SETFD respectively. Note L -> D. - To unsubscribe from this list: send the line

Re: close-exec flag not working in 2.6.9?

2005-01-31 Thread Ulrich Drepper
On Sun, 30 Jan 2005 23:56:07 -0800, Ben Greear [EMAIL PROTECTED] wrote: flags = fcntl(s, F_GETFL); flags |= (FD_CLOEXEC); if (fcntl(s, F_SETFL, flags) 0) { These have to be F_GETFD and F_SETFD respectively. Note L - D. - To unsubscribe from this list: send the line unsubscribe

Re: [PATCH 1/7] posix-timers: tidy up clock interfaces and consolidate dispatch logic

2005-01-24 Thread Ulrich Drepper
timing and see whether you can filter the difference out of the noise. -- â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â signature.asc Description: OpenPGP digital signature

Re: [PATCH 1/7] posix-timers: tidy up clock interfaces and consolidate dispatch logic

2005-01-24 Thread Ulrich Drepper
timing and see whether you can filter the difference out of the noise. -- Ulrich Drepper Red Hat, Inc. 444 Castro St Mountain View, CA signature.asc Description: OpenPGP digital signature

Re: Pollable Semaphores

2005-01-21 Thread Ulrich Drepper
On Fri, 21 Jan 2005 23:05:04 -0800, Chris Wright <[EMAIL PROTECTED]> wrote: > Yeah, here it is. I refreshed it against a current kernel. It passes my > same old test, where I select on /proc//status fd in exceptfds. Looks certainly attractive to me. Nice small patch. How quickly after the

Re: Pollable Semaphores

2005-01-21 Thread Ulrich Drepper
On Fri, 21 Jan 2005 17:17:51 -0600, Brent Casavant <[EMAIL PROTECTED]> wrote: > 2. select/poll on the fd return EWOULDBLOCK if the current value of > the futex is not equal to the value of interest. Otherwise it > behaves as FUTEX_FD currently does. This is the problematic part.

Re: Pollable Semaphores

2005-01-21 Thread Ulrich Drepper
On Fri, 21 Jan 2005 17:17:51 -0600, Brent Casavant [EMAIL PROTECTED] wrote: 2. select/poll on the fd return EWOULDBLOCK if the current value of the futex is not equal to the value of interest. Otherwise it behaves as FUTEX_FD currently does. This is the problematic part. The

Re: Pollable Semaphores

2005-01-21 Thread Ulrich Drepper
On Fri, 21 Jan 2005 23:05:04 -0800, Chris Wright [EMAIL PROTECTED] wrote: Yeah, here it is. I refreshed it against a current kernel. It passes my same old test, where I select on /proc/pid/status fd in exceptfds. Looks certainly attractive to me. Nice small patch. How quickly after the

Re: short read from /dev/urandom

2005-01-15 Thread Ulrich Drepper
cond: It still means the documented API says there are no short reads. So anyone doing a read() can expect a short read regardless of the fd and is quite clear that reads can be interrupted by signals. "It is not an error". Ever. Of course are signal interruptions wrong if the signal uses SA_

Re: short read from /dev/urandom

2005-01-15 Thread Ulrich Drepper
the documented API says there are no short reads. So anyone doing a read() can expect a short read regardless of the fd and is quite clear that reads can be interrupted by signals. It is not an error. Ever. Of course are signal interruptions wrong if the signal uses SA_RESTART. -- Ulrich Drepper Red Hat

Re: BUG: Global FPU corruption in 2.2

2001-04-20 Thread Ulrich Drepper
features of the processor first. The kernel can detect when the FPU is used for the first time. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `

Re: BUG: Global FPU corruption in 2.2

2001-04-20 Thread Ulrich Drepper
s was always the case and necessary to implement the fast lazy FPU saving/restoring. Processes which never use the FPU never initialize it. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat

Re: BUG: Global FPU corruption in 2.2

2001-04-20 Thread Ulrich Drepper
e case and necessary to implement the fast lazy FPU saving/restoring. Processes which never use the FPU never initialize it. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' d

Re: BUG: Global FPU corruption in 2.2

2001-04-20 Thread Ulrich Drepper
ssor first. The kernel can detect when the FPU is used for the first time. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To u

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
ing else I couldn't care less since it's useless for me. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from

Re: [linux-lvm] 2.4.3-ac{6,7} LVM hang

2001-04-19 Thread Ulrich Drepper
Jens Axboe <[EMAIL PROTECTED]> writes: > Does attached patch fix it? Yes. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at r

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
++*i; pthread_mutex_unlock (m1); pthread_mutex_lock (m2); } return 0; } ~~~~~~~ -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com `--

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
g this her/himself. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "u

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
t really care what the final implementation will be like. For UP and SMP machines I definitely want to have as much as possible at user-level. If you need a special libpthread for NUMA machines, so be it. -- ---. ,-. 1325 Chesapeake Terr

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
the file change? The kernel representation of the mutex must not be disassociated from the shared memory region. Even if you all think very little about Solaris, look at the kernel interface for semaphores. -- ---. ,-. 1325 Chesa

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
unix file permissions on them ? See above. Permissions are only allowed for named semaphores. -- -------. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com `--

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
fd = open (name) addr = mmap (..fd..) close (fd) sem_syscall (addr) i.e., it can be mapped to a memory reference again. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
r dealing with the common case without syscalls can be applied here as well. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at r

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
with the common case without syscalls can be applied here as well. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
..) close (fd) sem_syscall (addr) i.e., it can be mapped to a memory reference again. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
n them ? See above. Permissions are only allowed for named semaphores. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com `-

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
The kernel representation of the mutex must not be disassociated from the shared memory region. Even if you all think very little about Solaris, look at the kernel interface for semaphores. -- ---. ,-. 1325 Chesapeake Terrace Ulri

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
the final implementation will be like. For UP and SMP machines I definitely want to have as much as possible at user-level. If you need a special libpthread for NUMA machines, so be it. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" i

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
ad_mutex_unlock (m1); pthread_mutex_lock (m2); } return 0; } ~~~ -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 940

Re: [linux-lvm] 2.4.3-ac{6,7} LVM hang

2001-04-19 Thread Ulrich Drepper
Jens Axboe [EMAIL PROTECTED] writes: Does attached patch fix it? Yes. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com

Re: light weight user level semaphores

2001-04-19 Thread Ulrich Drepper
since it's useless for me. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line

Re: light weight user level semaphores

2001-04-18 Thread Ulrich Drepper
s. The rest seems OK. Thanks, -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the l

Re: light weight user level semaphores

2001-04-18 Thread Ulrich Drepper
t seems OK. Thanks, -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscri

Re: PATCH(?): linux-2.4.4-pre2: fork should run child first

2001-04-13 Thread Ulrich Drepper
arently want. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to

Re: PATCH(?): linux-2.4.4-pre2: fork should run child first

2001-04-13 Thread Ulrich Drepper
Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More

Re: List of all-zero .data variables in linux-2.4.3 available

2001-04-12 Thread Ulrich Drepper
rogrammers to not initialize. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the

Re: List of all-zero .data variables in linux-2.4.3 available

2001-04-12 Thread Ulrich Drepper
It is a programmer problem. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel&qu

Re: List of all-zero .data variables in linux-2.4.3 available

2001-04-12 Thread Ulrich Drepper
er problem. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message

Re: List of all-zero .data variables in linux-2.4.3 available

2001-04-12 Thread Ulrich Drepper
initialize. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [E

Re: struct stat{st_blksize} for /dev entries in 2.4.3

2001-04-08 Thread Ulrich Drepper
nd there is no guarantee that any of the _SC_* constants are defined as macros. You'll have to add a configure test. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 US

Re: struct stat{st_blksize} for /dev entries in 2.4.3

2001-04-08 Thread Ulrich Drepper
are defined as macros. You'll have to add a configure test. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from

Re: [PATCH] pcnet32 compilation fix for 2.4.3pre6

2001-03-29 Thread Ulrich Drepper
efully forever signal the gcc semantics. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send th

Re: [PATCH] pcnet32 compilation fix for 2.4.3pre6

2001-03-29 Thread Ulrich Drepper
forever signal the gcc semantics. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line

Re: RFC: changing precision control setting in initial FPU context

2001-03-03 Thread Ulrich Drepper
stupid idea. No kernel and no libc modifications necessary. This is the end of the story as far as I'm concerned. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `-

Re: RFC: changing precision control setting in initial FPU context

2001-03-03 Thread Ulrich Drepper
modifications necessary. This is the end of the story as far as I'm concerned. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com

Re: [PATCH] devfsd, compiling on glibc22x

2001-02-04 Thread Ulrich Drepper
wrote the code. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a me

Re: [PATCH] devfsd, compiling on glibc22x

2001-02-04 Thread Ulrich Drepper
. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECT

Re: [PATCH] devfsd, compiling on glibc22x

2001-01-27 Thread Ulrich Drepper
,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTE

Re: [PATCH] devfsd, compiling on glibc22x

2001-01-27 Thread Ulrich Drepper
Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the F

Re: [PATCH] new bug report script

2001-01-07 Thread Ulrich Drepper
you, as the other script suggested, execute libc.so.6? Symlinks can be missing or can be wrong. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com `---

Re: [PATCH] Re: [PATCH] new bug report script

2001-01-07 Thread Ulrich Drepper
/i486-linux-libc5/lib/libc.so.5 and then look in that directory (/usr/i486-linux-libc5/lib). -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To un

Re: [PATCH] new bug report script

2001-01-07 Thread Ulrich Drepper
.so files there). -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAI

<    2   3   4   5   6   7   8   >