All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: jkraehemann-guest@users.alioth.debian.org
Cc: linux-rt-users@vger.kernel.org
Subject: Re: deterministic usage of JIFFIES and how to relocate the clock
Date: Thu, 4 Feb 2016 17:44:11 +0100	[thread overview]
Message-ID: <20160204164411.GC3381@linutronix.de> (raw)
In-Reply-To: <CA+Owze7+=vMDaqX25OVQ6ZrRgGj9j2BZjEZt_GyG+9+6+6ELWA@mail.gmail.com>

* Joël Krähemann | 2016-01-24 09:40:33 [+0100]:

>Hi
Hi,

>At my opinion I was thinking at a lower level than needed. The
I couldn't parse the question in the previous mail.

>application runs at least aside the kernel.

aside the kernel? Like one CPU is for the kernel and the other for the
application?

>Probably I want to control PC (program counter) and redeclare the
>longjump function as macro. To gain control
>over throughput rate and thus being able to grain loading and unloading thread.

maybe. But I still fail to understand what you attempt to do.

>int sched_setaffinity(pid_t pid, size_t cpusetsize,
>                             const cpu_set_t *mask);

This one says which CPUs the task may run on.

>void longjmp(jmp_buf env, int val);

and this is unrelated to the previous one.

>
>cheers,
>Joël

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-02-04 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22  9:37 deterministic usage of JIFFIES and how to relocate the clock Joël Krähemann
2016-01-24  8:40 ` Joël Krähemann
2016-02-04 16:44   ` Sebastian Andrzej Siewior [this message]
2016-02-09 20:04     ` Joël Krähemann

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=20160204164411.GC3381@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=jkraehemann-guest@users.alioth.debian.org \
    --cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.