public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Brad Keifenheim <Brad_Keifenheim@Dell.com>
To: "pthreads-win32@sourceware.org" <pthreads-win32@sourceware.org>
Subject: Evaluation / Missing Prototypes
Date: Fri, 31 May 2013 22:42:00 -0000	[thread overview]
Message-ID: <975552A94CBC0F4DA60ED7B36C949CBA075D0C586B@shandy.Beer.Town> (raw)

Hello,

I'm evaluating using the Pthreads-Win32 library to port some internal software from FreeBSD to Windows here at Dell. I have coded a proof of concept and am impressed with the library. Unfortunately I would still be missing several calls for a complete port. Several of these calls are in the "non-portable" category, but nonetheless I'm wondering if any thought has been given to providing support. 
 
I would very much appreciate if you could have a look at my list and let me know if anything is in the works or already provided via a different mechanism.

pthread_set_name_np (Nice to have, but not essential)
pthread_mutexattr_setprotocol
pthread_suspend_all_np
pthread_mutex_isowned_np
pthread_kill (Would need more than just sig 0)
pthread_attr_setcreatesuspend_np
pthread_attr_setinheritsched (Need SCHED_FIFO)
pthread_attr_setguardsize (Nice to have, but not essential)
pthread_attr_setscope (Some legacy code uses PTHREAD_SCOPE_PROCESS, not a current requirement though)
pthread_attr_setaffinity_np
pthread_resume_np
pthread_attr_getstack
pthread_attr_getguardsize (Nice to have, but not essential)
pthread_getaffinity_np

Cheers,

Brad Keifenheim
Software Development Engineer
Dell | Compellent
brad_keifenheim@dell.com

                 reply	other threads:[~2013-05-31 22:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=975552A94CBC0F4DA60ED7B36C949CBA075D0C586B@shandy.Beer.Town \
    --to=brad_keifenheim@dell.com \
    --cc=pthreads-win32@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).