All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Takashi Iwai <tiwai@suse.de>, Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH v3] ALSA: control: Add memory consumption limit to user controls
Date: Fri, 9 Apr 2021 15:34:14 +0200	[thread overview]
Message-ID: <1c2da980-1f63-c6fe-a4c0-005a1ed5bc19@perex.cz> (raw)
In-Reply-To: <s5h5z0v67wh.wl-tiwai@suse.de>

Dne 09. 04. 21 v 12:59 Takashi Iwai napsal(a):

>> 5. add any mechanism to bind lifetime of user-defined element set to user
>>    process
>>
>> At present, the lifetime of user-defined element set is bound to card
>> itself. However, it's convenient to user processes to bind the lifetime
>> to process itself. I add any mechanism for it.
>>
>> For recent years I've made some patches in house but never arrive at the
>> best one. In the patches, I utilize access flags but in general the
>> maintenance of lifetime is not easy issue. I tackle again in this time.
> 
> It sounds interesting, but I don't know how easily you can manage it.
> The driver doesn't care much about the user process lifetime, but
> mostly concentrate on the file handle...

It should be easy to trace which process created the user element and
automatically remove this element when the process close the file descriptor.
Something like 'bind lifetime of the control to the active control file
descriptor'.

					Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

  reply	other threads:[~2021-04-09 13:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 10:31 [PATCH v3] ALSA: control: Add memory consumption limit to user controls Takashi Sakamoto
2021-04-08 10:50 ` Takashi Sakamoto
2021-04-08 11:33   ` Takashi Iwai
2021-04-09  2:27     ` Takashi Sakamoto
2021-04-09 10:59       ` Takashi Iwai
2021-04-09 13:34         ` Jaroslav Kysela [this message]
2021-04-09 14:18           ` Takashi Iwai
2021-04-10  8:22             ` Takashi Sakamoto
2021-04-10  8:56               ` Takashi Iwai
2021-04-09 16:09         ` Takashi Iwai
2021-04-10  8:20           ` Takashi Sakamoto
2021-04-10  8:47             ` Takashi Iwai
2021-04-18 14:15               ` Takashi Sakamoto
2021-04-18 14:27         ` Takashi Sakamoto
2021-04-18 18:42           ` Jaroslav Kysela

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=1c2da980-1f63-c6fe-a4c0-005a1ed5bc19@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=o-takashi@sakamocchi.jp \
    --cc=tiwai@suse.de \
    /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.