From: "Zhu, Lipeng" <lipeng.zhu@intel.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org,
rep.dot.nop@gmail.com, hongjiu.lu@intel.com,
tianyou.li@intel.com, pan.deng@intel.com, jakub@redhat.com,
wangyang.guo@intel.com
Subject: Re: [PATCH v4] libgfortran: Replace mutex with rwlock
Date: Thu, 25 May 2023 20:40:15 +0800 [thread overview]
Message-ID: <23405f0b-f2b0-86b2-c40c-96156908c02e@intel.com> (raw)
On 1/1/1970 8:00 AM, Thomas Koenig wrote:
> Hi Lipeng,
>
>> May I know any comment or concern on this patch, thanks for your time :)
>>
>
> Thanks for your patience in getting this reviewed.
>
> A few remarks / questions.
>
> Which strategy is used in this implementation, read-preferring or write-preferring? And if read-
> preferring is used, is there a danger of deadlock if people do unreasonable things?
> Maybe you could explain that, also in a comment in the code >
> Can you add some sort of torture test case(s) which does a lot of opening/closing/reading/writing,
> possibly with asynchronous I/O and/or pthreads, to catch possible problems? If there is a system
> dependency or some race condition, chances are that regression testers will catch this.
Hi Thomas,
Thanks for your time for the review.
Sure, I will add test case according to your suggestions and update the
comment based on the implementation of "read-preferring" strategy.
Thanks,
Lipeng Zhu
>
> With this, the libgfortran parts are OK, unless somebody else has more comments, so give this a couple
> of days. I cannot approve the libgcc parts, that would be somebody else (Jakub?)
>
> Best regards
>
> Thomas
>
>
next reply other threads:[~2023-05-25 12:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 12:40 Zhu, Lipeng [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-09 2:32 Zhu, Lipeng
2023-05-16 7:08 ` Zhu, Lipeng
2023-05-23 2:53 ` Zhu, Lipeng
2023-05-24 19:18 ` Thomas Koenig
2023-08-18 3:06 ` Zhu, Lipeng
2023-09-14 8:33 ` Zhu, Lipeng
2023-10-23 1:21 ` Zhu, Lipeng
2023-10-23 5:52 ` Thomas Koenig
2023-10-23 23:59 ` Zhu, Lipeng
2023-11-01 10:14 ` Zhu, Lipeng
2023-11-02 9:58 ` Bernhard Reutner-Fischer
2023-11-23 9:36 ` Zhu, Lipeng
2023-12-07 5:18 ` Zhu, Lipeng
[not found] <20230424214534.77117b73 () nbbrfq>
2023-05-08 9:44 ` Lipeng Zhu
2023-05-08 10:28 ` Bernhard Reutner-Fischer
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=23405f0b-f2b0-86b2-c40c-96156908c02e@intel.com \
--to=lipeng.zhu@intel.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongjiu.lu@intel.com \
--cc=jakub@redhat.com \
--cc=pan.deng@intel.com \
--cc=rep.dot.nop@gmail.com \
--cc=tianyou.li@intel.com \
--cc=tkoenig@netcologne.de \
--cc=wangyang.guo@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).