All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Dmitry Adamushko <dmitry.adamushko@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [RFC][PATCH] shirq locking rework
Date: Mon, 25 Jun 2007 22:29:30 +0200	[thread overview]
Message-ID: <468025AA.7080908@domain.hid> (raw)
In-Reply-To: <200706252111.40219.dmitry.adamushko@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]

Hi Dmitry,

Dmitry Adamushko wrote:
> Hello Jan,
> 
> well, take it with 2 huge grains of salt.. it's even not compile-tested :-)

Yeah, that might explain while already trying to parse it manually
failed: What is xnintr_sync_stat_references? :)

> 
> I don't think I've got it really nicer than your first patch.. the only additional point is that
> 'prev = xnstat_get_current()' reference is also tracked as reference accounting becomes
> a part of the xnstat interface (not sure we do need it though).

Mind to elaborate on _why_ you think we need this, specifically if it
adds new atomic counters? I'm too lazy looking for the probably valid
reason on my own. Apropos atomic use counters: already considered all
memory barrier issues for your locking scheme?

> 
> Well (#2), I have to say that the whole intr subsystem looks not that nice (maybe partly due
> to being overloaded with xnstat details).. so I think, it'd require a closer look.

Let's get it right first, then think about aesthetic or even concrete
optimisations again.

> 
> Anyway, here is what I've got out of your patch so far.. the main issue is whether we go this way
> or it just makes things even more uglier.

Again, correctness, race-avoidance worries me first right now.

> 
> (a side effect : I transformed xnstat_* macroses into 'static inline' function.. I guess, this way it's a bit nicer)

Uhh, be careful, I burned my fingers with similar things recently as
well. You have to make sure that all types are resolvable for _all_
includers of that header. Otherwise, I'm fine with cleanups like this.
But I think there was once a reason for #define.

Thanks,
Jan


PS: Please note my latest refactoring check-in to SVN, touching stat.h.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2007-06-25 20:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 19:11 [Xenomai-core] [RFC][PATCH] shirq locking rework Dmitry Adamushko
2007-06-25 20:29 ` Jan Kiszka [this message]
2007-06-30  8:36   ` Dmitry Adamushko
  -- strict thread matches above, loose matches on Subject: below --
2007-06-19 18:40 Jan Kiszka
2007-06-20 21:04 ` Dmitry Adamushko
2007-06-20 21:58   ` Jan Kiszka
2007-06-21  8:03     ` Dmitry Adamushko
2007-06-21  9:20       ` Jan Kiszka
2007-06-21  9:52         ` Dmitry Adamushko
2007-06-21 12:56           ` Jan Kiszka
2007-06-21 13:14             ` Dmitry Adamushko
2007-06-21 13:40               ` Jan Kiszka
2007-06-22 11:53                 ` Jan Kiszka
2007-06-22 12:17                   ` Dmitry Adamushko
2007-06-22 12:24                     ` Jan Kiszka
     [not found]         ` <467A5B85.9010103@domain.hid>
2007-06-21 17:24           ` Philippe Gerum
2007-06-21 17:46             ` Jan Kiszka

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=468025AA.7080908@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=dmitry.adamushko@domain.hid \
    --cc=xenomai@xenomai.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.