From: Ulrich Drepper <drepper@gmail.com>
To: Kalaky <kalaky@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] sigpending rework
Date: Mon, 13 Dec 2004 17:14:56 -0800 [thread overview]
Message-ID: <a36005b504121317145f144cd1@mail.gmail.com> (raw)
In-Reply-To: <4de0ceaa04121315064b9643c1@mail.gmail.com>
On Mon, 13 Dec 2004 21:06:08 -0200, Kalaky <kalaky@gmail.com> wrote:
>
> 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.
This looks like a logical extension but the question is, is it worth
it? I don't know about a case so far where this is a bottle neck.
But any solution will cost every process, regardless of whether it
uses signals often or not.
So, if your solution can avoid or keep the cost very very low, it
might be worth using such a change. Otherwise the ol' saying applies:
avoid signals at all costs.
prev parent reply other threads:[~2004-12-14 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 23:06 [RFC] sigpending rework Kalaky
2004-12-14 1:14 ` Ulrich Drepper [this message]
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=a36005b504121317145f144cd1@mail.gmail.com \
--to=drepper@gmail.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).