From: "Chanho Min" <chanho.min@lge.com>
To: 'Takashi Iwai' <tiwai@suse.de>
Cc: 'Jaroslav Kysela' <perex@perex.cz>,
'Takashi Iwai' <tiwai@kernel.org>,
'Vinod Koul' <vkoul@kernel.org>,
'Daniel Mentz' <danielmentz@google.com>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
'Seungho Park' <seungho1.park@lge.com>,
'Jongsung Kim' <neidhard.kim@lge.com>,
'Wonmin Jung' <wonmin.jung@lge.com>,
'Jaehyun Kim' <jehn.kim@lge.com>,
'Hyonwoo Park' <hyonwoo.park@lge.com>
Subject: RE: [PATCH] ALSA: pcm: Fix starvation on down_write_nonblock()
Date: Wed, 28 Nov 2018 08:47:03 +0900 [thread overview]
Message-ID: <1aaf01d486ab$8017a5b0$8046f110$@lge.com> (raw)
In-Reply-To: <s5hin0k6xqy.wl-tiwai@suse.de>
> On Mon, 26 Nov 2018 06:36:37 +0100,
> Chanho Min wrote:
> >
> > Commit 67ec1072b053 ("ALSA: pcm: Fix rwsem deadlock for non-atomic PCM
> > stream") fixes deadlock for non-atomic PCM stream. But, This patch
> causes antother stuck.
> > If writer is RT thread and reader is a normal thread, the reader
> > thread will be difficult to get scheduled. It may not give chance to
> > release readlocks and writer gets stuck for a long time if they are
> pinned to single cpu.
> >
> > The deadlock described in the previous commit is because the linux
> > rwsem queues like a FIFO. So, we might need non-FIFO writelock, not non-
> block one.
> >
> > My suggestion is that the writer gives reader a chance to be scheduled
> > by using the minimum msleep() instaed of spinning without blocking by
> > writer. Also, The *_nonblock may be changed to *_nonfifo appropriately
> to this concept.
> > In terms of performance, when trylock is failed, this minimum periodic
> > msleep will have the same performance as the tick-based
> schedule()/wake_up_q().
> >
> > Suggested-by: Wonmin Jung <wonmin.jung@lge.com>
> > Signed-off-by: Chanho Min <chanho.min@lge.com>
>
> Hrm, converting unconditionally with msleep() looks too drastic.
Yes, it looks drastic. But, IMHO, I can't say busy-spin is not non-drastic.
To fix the root cause, We may need another rwsem that does not work as a
FIFO.
>
> I guess you've hit this while not explicitly using the linked PCM streams,
> i.e. in the call of snd_pcm_unlink() at close, right?
>
> Then this can be worked around by checking the link before calling it.
> Could you check the patch below?
More testing is needed, but it seems to be fixed by your patch.
We may not use the linked PCM.
But, If the linked PCM is enabled, Can snd_pcm_unlink() be called?
This also seems to be a workaround.
>
>
> thanks,
>
> Takashi
>
> --- a/sound/core/pcm_native.c
> +++ b/sound/core/pcm_native.c
> @@ -2369,7 +2369,8 @@ int snd_pcm_hw_constraints_complete(struct
> snd_pcm_substream *substream)
>
> static void pcm_release_private(struct snd_pcm_substream *substream) {
> - snd_pcm_unlink(substream);
> + if (snd_pcm_stream_linked(substream))
> + snd_pcm_unlink(substream);
> }
>
> void snd_pcm_release_substream(struct snd_pcm_substream *substream)
WARNING: multiple messages have this Message-ID (diff)
From: "Chanho Min" <chanho.min@lge.com>
To: "'Takashi Iwai'" <tiwai@suse.de>
Cc: "'Jaroslav Kysela'" <perex@perex.cz>,
"'Takashi Iwai'" <tiwai@kernel.org>,
"'Vinod Koul'" <vkoul@kernel.org>,
"'Daniel Mentz'" <danielmentz@google.com>,
<linux-kernel@vger.kernel.org>, <alsa-devel@alsa-project.org>,
"'Seungho Park'" <seungho1.park@lge.com>,
"'Jongsung Kim'" <neidhard.kim@lge.com>,
"'Wonmin Jung'" <wonmin.jung@lge.com>,
"'Jaehyun Kim'" <jehn.kim@lge.com>,
"'Hyonwoo Park'" <hyonwoo.park@lge.com>
Subject: RE: [PATCH] ALSA: pcm: Fix starvation on down_write_nonblock()
Date: Wed, 28 Nov 2018 08:47:03 +0900 [thread overview]
Message-ID: <1aaf01d486ab$8017a5b0$8046f110$@lge.com> (raw)
In-Reply-To: <s5hin0k6xqy.wl-tiwai@suse.de>
> On Mon, 26 Nov 2018 06:36:37 +0100,
> Chanho Min wrote:
> >
> > Commit 67ec1072b053 ("ALSA: pcm: Fix rwsem deadlock for non-atomic PCM
> > stream") fixes deadlock for non-atomic PCM stream. But, This patch
> causes antother stuck.
> > If writer is RT thread and reader is a normal thread, the reader
> > thread will be difficult to get scheduled. It may not give chance to
> > release readlocks and writer gets stuck for a long time if they are
> pinned to single cpu.
> >
> > The deadlock described in the previous commit is because the linux
> > rwsem queues like a FIFO. So, we might need non-FIFO writelock, not non-
> block one.
> >
> > My suggestion is that the writer gives reader a chance to be scheduled
> > by using the minimum msleep() instaed of spinning without blocking by
> > writer. Also, The *_nonblock may be changed to *_nonfifo appropriately
> to this concept.
> > In terms of performance, when trylock is failed, this minimum periodic
> > msleep will have the same performance as the tick-based
> schedule()/wake_up_q().
> >
> > Suggested-by: Wonmin Jung <wonmin.jung@lge.com>
> > Signed-off-by: Chanho Min <chanho.min@lge.com>
>
> Hrm, converting unconditionally with msleep() looks too drastic.
Yes, it looks drastic. But, IMHO, I can't say busy-spin is not non-drastic.
To fix the root cause, We may need another rwsem that does not work as a
FIFO.
>
> I guess you've hit this while not explicitly using the linked PCM streams,
> i.e. in the call of snd_pcm_unlink() at close, right?
>
> Then this can be worked around by checking the link before calling it.
> Could you check the patch below?
More testing is needed, but it seems to be fixed by your patch.
We may not use the linked PCM.
But, If the linked PCM is enabled, Can snd_pcm_unlink() be called?
This also seems to be a workaround.
>
>
> thanks,
>
> Takashi
>
> --- a/sound/core/pcm_native.c
> +++ b/sound/core/pcm_native.c
> @@ -2369,7 +2369,8 @@ int snd_pcm_hw_constraints_complete(struct
> snd_pcm_substream *substream)
>
> static void pcm_release_private(struct snd_pcm_substream *substream) {
> - snd_pcm_unlink(substream);
> + if (snd_pcm_stream_linked(substream))
> + snd_pcm_unlink(substream);
> }
>
> void snd_pcm_release_substream(struct snd_pcm_substream *substream)
next prev parent reply other threads:[~2018-11-27 23:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 5:36 [PATCH] ALSA: pcm: Fix starvation on down_write_nonblock() Chanho Min
2018-11-26 8:36 ` Takashi Iwai
2018-11-27 23:47 ` Chanho Min [this message]
2018-11-27 23:47 ` Chanho Min
2018-11-28 8:37 ` Takashi Iwai
2018-11-28 8:37 ` Takashi Iwai
2018-11-28 23:48 ` Chanho Min
2018-11-28 23:48 ` Chanho Min
2018-11-29 7:19 ` Takashi Iwai
2018-11-29 7:19 ` Takashi Iwai
2018-11-29 23:03 ` Chanho Min
2018-11-29 23:03 ` Chanho Min
2018-11-28 6:26 ` Chanho Min
2018-11-28 6:26 ` Chanho Min
-- strict thread matches above, loose matches on Subject: below --
2018-11-24 7:32 Chanho Min
2018-11-24 7:32 ` Chanho Min
2018-11-24 10:56 ` kbuild test robot
2018-11-24 10:56 ` kbuild test robot
2018-11-25 11:30 ` kbuild test robot
2018-11-25 11:30 ` kbuild test robot
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='1aaf01d486ab$8017a5b0$8046f110$@lge.com' \
--to=chanho.min@lge.com \
--cc=alsa-devel@alsa-project.org \
--cc=danielmentz@google.com \
--cc=hyonwoo.park@lge.com \
--cc=jehn.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neidhard.kim@lge.com \
--cc=perex@perex.cz \
--cc=seungho1.park@lge.com \
--cc=tiwai@kernel.org \
--cc=tiwai@suse.de \
--cc=vkoul@kernel.org \
--cc=wonmin.jung@lge.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.