From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Why is taskset still not in util-linux?
Date: Thu, 19 Mar 2020 11:41:00 +0100 [thread overview]
Message-ID: <bef62c6e-19a5-43a8-2889-1baf59230d2b@gmail.com> (raw)
In-Reply-To: <01e3d337-e5fe-f393-7634-3f1881bca315@cs.umass.edu>
Am 19.03.2020 um 11:14 schrieb Eliot Moss:
> On 3/16/2020 7:34 PM, Mark Geisert wrote:
> > Mark Geisert wrote:
> >> Eliot Moss wrote:
> >>>
> >>> Dear cygwin-ers --
> >>>
> >>> Something I had asked about a while ago was the absence os taskset
> in cygwin's
> >>> util-linux. At the time, it was pointed out that the necessary
> get/set
> >>> affinity library/system calls were not yet supported. These were
> added a
> >>> while ago, so it would seem that taskset ought to work. In fact, I
> think
> >>> someone got it going on their own. Can we add it to util-linux now,
> >>> officially? I think this was intended but perhaps was overlooked or
> >>> something.
> >>
> >> Report noted; thanks. A solution is being worked.
> >
> > There's been no forward progress on this. If you're comfortable
> getting the util-linux source
> > package through Cygwin setup*.exe, you can follow the steps shown in
> > https://cygwin.com/pipermail/cygwin-apps/2020-March/039855.html to
> build (with cygport) a local copy
> > of util-linux that includes a taskset.exe you can move into
> /usr/local/bin, for example.
> >
> > You might try that route if you're up for it. Feel free to ask
> questions here if you hit a snag.
> > HTH,
>
> Thank you, Mark. I decided to give it a try and got some distance, but
> hit a snag.
>
> First, I had to change configure.ac to add control to disable ionice
> (Cygwin
> does not support a required syscall) while still trying to build taskset.
> Previously taskset and ionice (and one other program) were controlled by
> the
> single --enable-schedutils.
>
> Now, including sched.h does not provide the prototypes for
> sched_getaffinity,
> etc. I found a previous post that suggests we need to do -D_GNU_SOURCE
> for it
> to work. I am not sure of the best place to stick that, but I will see
> about
> maybe a one line patch to taskset.c or something.
>
> Regards - Eliot
one brutal solution I recently used
cygconf
echo "defining _GNU_SOURCE on config.h"
echo "#define _GNU_SOURCE 1" >> config.h
cygmake
the patch approach is usually restricted to a portion
of the code or a general header.
May be there is already something like that in the code,
or you can add a similar stuff
#if defined(__linux__) || defined(__CYGWIN__)
# ifndef _GNU_SOURCE
# define _GNU_SOURCE
# endif
next prev parent reply other threads:[~2020-03-19 10:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 21:46 Eliot Moss
2020-03-04 13:32 ` Mark Geisert
2020-03-16 23:34 ` Mark Geisert
2020-03-19 10:14 ` Eliot Moss
2020-03-19 10:41 ` Marco Atzeri [this message]
2020-03-19 23:29 ` Mark Geisert
2020-03-20 5:54 ` Mark Geisert
2020-03-20 10:29 ` Eliot Moss
2020-03-20 21:42 ` Andrey Repin
2020-03-20 13:39 ` Yaakov Selkowitz
2020-03-21 1:46 ` Eliot Moss
2020-03-21 8:37 ` Mark Geisert
2020-03-21 10:24 ` Eliot Moss
2020-03-21 11:07 ` Eliot Moss
2020-03-21 13:29 ` Marco Atzeri
2020-03-21 14:26 ` Roumen Petrov
2020-03-21 23:13 ` Eliot Moss
2020-03-22 4:10 ` Eliot Moss
2020-03-22 5:20 ` Eliot Moss
2020-03-24 8:09 ` Mark Geisert
2020-03-24 8:16 ` Eliot Moss
2020-03-22 20:09 ` Yaakov Selkowitz
2020-03-21 4:59 ` Eliot Moss
2020-03-21 8:18 ` Mark Geisert
2020-03-21 16:41 ` Brian Inglis
2020-03-23 9:31 ` Corinna Vinschen
2020-03-23 9:42 ` Mark Geisert
2020-03-23 18:48 ` Brian Inglis
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=bef62c6e-19a5-43a8-2889-1baf59230d2b@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/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).