All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Subject: Re: [Ksummit-discuss] Complex dependencies - tech topic notes
Date: Tue, 8 Nov 2016 02:27:59 +0530	[thread overview]
Message-ID: <20161107205759.GN3000@localhost> (raw)
In-Reply-To: <CAB=NE6XYBj0h7rYL8yWwACUHF7ni0AMeCe4Rf2dfbjRQ=KY78g@mail.gmail.com>

On Mon, Nov 07, 2016 at 12:39:51PM -0800, Luis R. Rodriguez wrote:
> Here are my own notes from what ended up being 2 sessions, 1
> whiteboard session followed up by a few other hallway tracks from the
> complex dependency tech topic at KS/Plumbers. Please provide your own
> notes or feel free to help complete some points below if you have
> anything to contribute, or let's just follow up through patch review
> on Rafael's and Andrzej's work -- I'll be doing this in light of the
> below notes.
> 
> My original goal really was to narrow down which subsystems might use
> a graph to express dependencies, and which might perform a topological
> sort on that graph in the kernel. The end goal being if we could
> abstract and share a solution rather than re-inventing the wheel. Then
> review this in consideration of Rafael's new patches on functional
> dependencies, Andrzej Hajda's new patches on Resource tracking /
> allocation tracking. As expressed in the threads and in the sessions
> though there was an ultimate suspicion this could also help as an
> optimization with probe ordering and to help replace deferred probe,
> this turned out to be the main focus of much of the white board
> session. The itemized list below represents some areas of the kernel
> that came out through hallway tracks follow up discussions.
> 
> Other topics reviewed were dependency cycle resolution and generic
> drivers. Cycles may arise due to topology changes (for instance
> hotplug), and if cycles exist in the worst case we end up with an
> NP-complete order problem, otherwise its a linear problem. One simple
> proposal for cycle resolution that everyone seemed to reach consensus
> for was to strive towards using a graph representation for devices per
> operation or type of device. The topic of Generic drivers was pretty
> broad on its own so we left this out.
> 
> Sadly Andrzej Hajda was not present, nor was anyone familiar with his
> patches... so most review was done in light of Rafael's patches now
> merged in Greg's tree.
> 
> So to recap -- are there areas in the kernel where we implement and
> use a topological sort
> on a graph ? What algorithms are used and could we abstract such code and
> share it between subsystems ?
> 
> A) DAPM (Dynamic Audio Power Management)
> - Summary: TBD

Here are Audio WS notes which have the cross session notes as well

http://mailman.alsa-project.org/pipermail/alsa-devel/2016-November/114279.html

-- 
~Vinod

      reply	other threads:[~2016-11-07 20:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07 20:39 [Ksummit-discuss] Complex dependencies - tech topic notes Luis R. Rodriguez
2016-11-07 20:57 ` Vinod Koul [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=20161107205759.GN3000@localhost \
    --to=vinod.koul@intel.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=mcgrof@kernel.org \
    --cc=mchehab@osg.samsung.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.