All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [Patch] support of lock profiling in Xen
Date: Thu, 08 Oct 2009 11:35:47 +0200	[thread overview]
Message-ID: <4ACDB273.1090909@ts.fujitsu.com> (raw)
In-Reply-To: <C6F36D8C.16DCA%keir.fraser@eu.citrix.com>

Keir Fraser wrote:
> On 08/10/2009 10:04, "Juergen Gross" <juergen.gross@ts.fujitsu.com> wrote:
> 
>>>> It would even be possible to define lock arrays if summing up all data for
>>>> e.g. domain specific locks is not desired.
>>> Allowing spinlock_init() to specify not only a name but also a
>>> 'category-specific index' might be okay. For example, domid, in the case of
>>> a domain-specific lock. Hiding the allocation of profiling info structs in
>>> the spinlock subsystem somehow... (e.g., radix tree to make a simple
>>> growable array).
>> I'll try another patch...
> 
> Well, see my email just now. I could perhaps live with perfc-style
> declarations after all... Because this might make sense if locks can be
> broadly categorised as global or as per-domain, and it could avoid you
> having to make your implementation much more complex?
> 
> After all, now I think about it, an 'arbitrary' index specified to
> spinlock_init() is just making our lives more complicated if it will
> basically *always* be a domid. And knowing at a higher level which locks are
> actually per-domain could help your pretty printing?

I thought in this direction, too.
I would, however, try not to limit it to per domain locks, even if the first
implementation would support only global locks and per domain locks.

The perfc style declarations should only be necessary for the dynamically
initialized locks, and those could live near the domain structure definition
(or any other structure where they are needed).

I think the statically defined locks can be handled via an own data section
requiring no centrally defined index.


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 636 47950
Fujitsu Technolgy Solutions               e-mail: juergen.gross@ts.fujitsu.com
Otto-Hahn-Ring 6                        Internet: ts.fujitsu.com
D-81739 Muenchen                 Company details: ts.fujitsu.com/imprint.html

  reply	other threads:[~2009-10-08  9:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08  7:48 [Patch] support of lock profiling in Xen Juergen Gross
2009-10-08  8:15 ` Keir Fraser
2009-10-08  8:27   ` Juergen Gross
2009-10-08  8:38     ` Keir Fraser
2009-10-08  8:40     ` Keir Fraser
2009-10-08  9:04       ` Juergen Gross
2009-10-08  9:21         ` Keir Fraser
2009-10-08  9:35           ` Juergen Gross [this message]
2009-10-08  9:47             ` Keir Fraser
2009-10-09  8:27               ` Juergen Gross
2009-10-09  9:22                 ` Keir Fraser
2009-10-13 13:56                   ` Juergen Gross
2009-10-13 15:49                     ` Keir Fraser
2009-10-08  8:21 ` Keir Fraser
2009-10-08  8:38   ` Juergen Gross
2009-10-08  9:17     ` Keir Fraser
2009-10-09 10:35     ` George Dunlap

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=4ACDB273.1090909@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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 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.