From: YASUAKI ISHIMATSU <yasu.isimatu@gmail.com>
To: joeyli <jlee@suse.com>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Michal Hocko <mhocko@kernel.org>,
yasu.isimatu@gmail.com
Subject: Re: A udev rule to serve the change event of ACPI container?
Date: Thu, 3 Aug 2017 11:37:37 -0400 [thread overview]
Message-ID: <8c04a96f-3f7a-1c31-9522-3344a4751d33@gmail.com> (raw)
In-Reply-To: <20170802054939.GL2946@linux-l9pv.suse>
On 08/02/2017 01:49 AM, joeyli wrote:
> Hi YASUAKI,
>
> On Tue, Aug 01, 2017 at 03:21:38PM -0400, YASUAKI ISHIMATSU wrote:
>> Hi Joey,
>>
>> On 07/23/2017 05:18 AM, joeyli wrote:
> [...snip]
>>>>>
>>>>
>>>> At least Yasuaki raised similar behavior for container in 2013.
>>>> It's similar to the DVD player case, user space application needs
>>>> to do something then trigger children offline and ejection of
>>>> container.
>>>>
>>>> Base on Yasuaki's explanation, the reason of that he requested the
>>>> userland ejection approach is that he got memory hot-remove problem
>>>> in 2013. Maybe his problem is already fixed by your patches in current
>>>> mainline.
>>>>
>>>> Hi Yasuaki, could you please check that your memory hot-remove problem
>>>> is fixed on mainline kernel?
>>
>> I cannot remember what I mentioned in 2013. Could you tell me url of lkml archive.
>>
>
> Here: https://lkml.org/lkml/2013/11/28/520
Thank you for specifying the URL. In the URL, I wrote the following problems:
> 1. easily fail
> My container device has CPU device and Memory device, and maximum size of
> memory is 3Tbyte. In my environment, hot removing container device fails
> on offlining memory if memory is used by application.
> I think if offlininig memory, we must retly to offline memory several
> times.
I think the issue still remains. If process keeps accessing memory, offlining
the memory easily fails with EBUSY.
Thanks,
Yasuaki Ishimatsu
>
> In the mail, you mentioned two problems. But there have no detail about
> those issues, and no root causes. We don't know why kernel should relies
> on user space to complete the hot removing process for container.
>
> Thank a lot!
> Joey Lee
>
next prev parent reply other threads:[~2017-08-03 15:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 6:26 joeyli
2017-06-26 8:59 ` Michal Hocko
2017-07-11 8:25 ` Michal Hocko
2017-07-13 6:58 ` joeyli
2017-07-13 7:06 ` Michal Hocko
2017-07-13 12:45 ` joeyli
2017-07-14 8:37 ` Michal Hocko
2017-07-14 14:44 ` joeyli
2017-07-17 9:05 ` Michal Hocko
2017-07-19 9:09 ` joeyli
2017-07-24 8:57 ` Michal Hocko
2017-07-24 9:29 ` joeyli
2017-07-25 12:48 ` Michal Hocko
2017-07-31 7:38 ` joeyli
2017-08-02 9:01 ` Michal Hocko
2017-08-03 9:22 ` joeyli
2017-08-03 9:31 ` Michal Hocko
2017-08-03 9:52 ` joeyli
2017-08-03 11:25 ` Michal Hocko
2017-07-23 9:18 ` joeyli
2017-08-01 19:21 ` YASUAKI ISHIMATSU
2017-08-02 5:49 ` joeyli
2017-08-03 15:37 ` YASUAKI ISHIMATSU [this message]
2017-08-04 15:06 ` Michal Hocko
2017-08-15 10:04 ` joeyli
2017-06-28 19:53 ` YASUAKI ISHIMATSU
2017-06-29 3:57 ` joeyli
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=8c04a96f-3f7a-1c31-9522-3344a4751d33@gmail.com \
--to=yasu.isimatu@gmail.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jlee@suse.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=rafael.j.wysocki@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
all inboxes | Powered by JetHome®