From: Christopher Quinn <cq@htec.demon.co.uk>
To: Christopher Quinn <cq@htec.demon.co.uk>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: finer grained threading?
Date: Thu, 15 Aug 2002 16:00:06 +0100 [thread overview]
Message-ID: <3D5BC1F6.1040001@htec.demon.co.uk> (raw)
In-Reply-To: 3D5BBB61.7050305@htec.demon.co.uk
Ah! As suspected I am not the first to think about this! I have just
found a DECthreads page mentioning upcalls and the ability to switch
threads on a page fault event.
Is it correct to say LinuxThreads(pthreads impl.) cannot offer this feature?
Any suggestions for alternative thread packages for linux that do?
cheers,
chris Q.
Christopher Quinn wrote:
> hi list,
>
> I have been wondering about what happens to a locked resource within a
> set of kernel threads when the holding thread causes a page fault, say
> via touching a page of a mmap'ed file.
>
> As far as I can see, there is no system call API means for the
> thread/process to take remedial action when this I/O delay occurs -
> ie. it could be useful for the holding thread to yield its lock on the
> resource, allowing other threads to progress while it sleeps.
>
> Does anyone know otherwise?
>
> Is there any mechanism in the kernel allowing notification of a page
> fault event (or indeed other I/O related events) to be received by, say,
> some code encapsulated in a kernel module? ie. would writing a kernel
> module be any sort of option for me?
>
> hope that's clear.
> thanks,
> chris Q.
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
rgrds,
Chris Quinn
next prev parent reply other threads:[~2002-08-15 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 14:48 About getopt() William N. Zanatta
2002-08-08 17:41 ` Glynn Clements
2002-08-15 14:32 ` finer grained threading? Christopher Quinn
2002-08-15 15:00 ` Christopher Quinn [this message]
2002-08-15 15:37 ` Christopher Quinn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D5BC1F6.1040001@htec.demon.co.uk \
--to=cq@htec.demon.co.uk \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).