mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Dongli Zhang <dongli.zhang@oracle.com>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Cc: boris.ostrovsky@oracle.com, ian.jackson@eu.citrix.com,
	wei.liu2@citrix.com, srinivas.eeda@oracle.com
Subject: Re: [RFC 0/2] To introduce xenwatch multithreading (xen mtwatch)
Date: Sat, 7 Apr 2018 13:59:05 +0200	[thread overview]
Message-ID: <5c8c5c98-c16f-2df4-8582-90b5facc9f54@suse.com> (raw)
In-Reply-To: <1523100355-27647-1-git-send-email-dongli.zhang@oracle.com>

On 07/04/18 13:25, Dongli Zhang wrote:
> This is to introduce "xenwatch multithreading" (or "multithreaded xenwatch",
> abbreviated as 'mtwatch'). The implementation of xen mtwatch involves below
> components:
> 
> * dom0 linux kernel
> * xen toolstack
> 
> Here are what the RFC is going to discuss:
> 
> - what is the problem
> - what is the objective
> - what is the solution

Instead of creating one thread per domU, wouldn't it make much more
sense to use another mechanism, e.g. a workqueue, to deliver the
watch events? This would be one central place, wouldn't need any
changes in Xen tools or complex mechanisms to select the correct
thread, save resources, and domUs would benefit, too.


Juergen

  parent reply	other threads:[~2018-04-07 11:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-07 11:25 Dongli Zhang
2018-04-07 11:25 ` [PATCH RFC linux 1/2] xenbus: introduce xenwatch multithreading to dom0 linux kernel Dongli Zhang
2018-04-07 11:25 ` [PATCH RFC xen 2/2] libxl: introduce xenwatch multithreading to xen toolstack Dongli Zhang
2018-04-07 11:59 ` Juergen Gross [this message]
2018-04-07 14:22   ` [Xen-devel] [RFC 0/2] To introduce xenwatch multithreading (xen mtwatch) Dongli Zhang
2018-04-23 14:09 ` Wei Liu
2018-04-23 23:55   ` [Xen-devel] " Dongli Zhang
2018-04-24  5:22     ` Juergen Gross
2018-04-24  5:52       ` Dongli Zhang
2018-04-24  6:03         ` Juergen Gross
2018-04-24  6:10           ` Dongli Zhang
2018-04-24  6:23             ` Juergen Gross

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=5c8c5c98-c16f-2df4-8582-90b5facc9f54@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=dongli.zhang@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.eeda@oracle.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®