From: Kalaky <kalaky@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [RFC] sigpending rework
Date: Mon, 13 Dec 2004 21:06:08 -0200 [thread overview]
Message-ID: <4de0ceaa04121315064b9643c1@mail.gmail.com> (raw)
Hello,
Currently, queued RT signals go into a list of pending signals
for a given task_struct (multiple RT signals can be queued).
When an process dequeues a signal through sigwaitinfo()
we must search the list for the given signal. This search is
always O(n) where n is the number of pending signals,
since we must go through all list members to ensure if
a signal number is still pending.
I'm working on converting the sigpending structure into a vector
of _NSIG sigqueue's for each signal number (which is quite a big
work), this way we can directly access each signal list, delivering
and checking any pending signals in a efficient manner.
Any thoughts ?
TIA,
Kalaky
next reply other threads:[~2004-12-13 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 23:06 Kalaky [this message]
2004-12-14 1:14 ` [RFC] sigpending rework Ulrich Drepper
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=4de0ceaa04121315064b9643c1@mail.gmail.com \
--to=kalaky@gmail.com \
--cc=linux-kernel@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