On Thu, Dec 06, 2018 at 08:26:22AM +0800, Wei Yang wrote:
> Currently locking for memory hotplug is a little complicated.
>
> Generally speaking, we leverage the two global lock:
>
> * device_hotplug_lock
> * mem_hotplug_lock
>
> to serialise the process.
>
> While for the long term, we
Locking Internal section exists in core-api documentation, which is more
suitable for this.
This patch removes the duplication part here.
Signed-off-by: Wei Yang
Reviewed-by: David Hildenbrand
Acked-by: Mike Rapoport
---
Documentation/admin-guide/mm/memory-hotplug.rst | 40
Currently locking for memory hotplug is a little complicated.
Generally speaking, we leverage the two global lock:
* device_hotplug_lock
* mem_hotplug_lock
to serialise the process.
While for the long term, we are willing to have more fine-grained lock
to provide higher scalability.
This
On Wed, Dec 05, 2018 at 01:13:10PM +0100, Michal Hocko wrote:
>On Wed 05-12-18 10:34:26, Wei Yang wrote:
>> Currently locking for memory hotplug is a little complicated.
>>
>> Generally speaking, we leverage the two global lock:
>>
>> * device_hotplug_lock
>> * mem_hotplug_lock
>>
>> to
On Wed 05-12-18 10:34:26, Wei Yang wrote:
> Currently locking for memory hotplug is a little complicated.
>
> Generally speaking, we leverage the two global lock:
>
> * device_hotplug_lock
> * mem_hotplug_lock
>
> to serialise the process.
>
> While for the long term, we are willing to
On Wed 05-12-18 10:34:25, Wei Yang wrote:
> Locking Internal section exists in core-api documentation, which is more
> suitable for this.
>
> This patch removes the duplication part here.
>
> Signed-off-by: Wei Yang
Yes this doesn't really make any sense in an admin guide. It is a pure
Signed-off-by: James (Qian) Wang
---
Documentation/gpu/drivers.rst| 1 +
Documentation/gpu/komeda-kms.rst | 483 +++
2 files changed, 484 insertions(+)
create mode 100644 Documentation/gpu/komeda-kms.rst
diff --git a/Documentation/gpu/drivers.rst
Signed-off-by: James (Qian) Wang
---
Documentation/gpu/drivers.rst| 1 +
Documentation/gpu/komeda-kms.rst | 483 +++
2 files changed, 484 insertions(+)
create mode 100644 Documentation/gpu/komeda-kms.rst
diff --git a/Documentation/gpu/drivers.rst
On Wed, Dec 05, 2018 at 10:40:45AM +0200, Mike Rapoport wrote:
>On Wed, Dec 05, 2018 at 10:34:26AM +0800, Wei Yang wrote:
>> Currently locking for memory hotplug is a little complicated.
>>
>> Generally speaking, we leverage the two global lock:
>>
>> * device_hotplug_lock
>> *
On Wed, Dec 05, 2018 at 09:08:47AM +0100, David Hildenbrand wrote:
>On 05.12.18 03:34, Wei Yang wrote:
>> Currently locking for memory hotplug is a little complicated.
>>
>> Generally speaking, we leverage the two global lock:
>>
>> * device_hotplug_lock
>> * mem_hotplug_lock
>>
>> to
On Wed, Dec 05, 2018 at 10:30:13AM +0200, Mike Rapoport wrote:
>On Wed, Dec 05, 2018 at 09:03:24AM +0100, David Hildenbrand wrote:
>> On 05.12.18 03:34, Wei Yang wrote:
>> > Locking Internal section exists in core-api documentation, which is more
>> > suitable for this.
>> >
>> > This patch
On Wed, Dec 05, 2018 at 09:03:24AM +0100, David Hildenbrand wrote:
>On 05.12.18 03:34, Wei Yang wrote:
>> Locking Internal section exists in core-api documentation, which is more
>> suitable for this.
>>
>> This patch removes the duplication part here.
>>
>> Signed-off-by: Wei Yang
>> ---
>>
On Wed, Dec 05, 2018 at 10:34:26AM +0800, Wei Yang wrote:
> Currently locking for memory hotplug is a little complicated.
>
> Generally speaking, we leverage the two global lock:
>
> * device_hotplug_lock
> * mem_hotplug_lock
>
> to serialise the process.
>
> While for the long term, we
On Wed, Dec 05, 2018 at 09:03:24AM +0100, David Hildenbrand wrote:
> On 05.12.18 03:34, Wei Yang wrote:
> > Locking Internal section exists in core-api documentation, which is more
> > suitable for this.
> >
> > This patch removes the duplication part here.
> >
> > Signed-off-by: Wei Yang
> >
On 05.12.18 03:34, Wei Yang wrote:
> Currently locking for memory hotplug is a little complicated.
>
> Generally speaking, we leverage the two global lock:
>
> * device_hotplug_lock
> * mem_hotplug_lock
>
> to serialise the process.
>
> While for the long term, we are willing to have more
On 05.12.18 03:34, Wei Yang wrote:
> Locking Internal section exists in core-api documentation, which is more
> suitable for this.
>
> This patch removes the duplication part here.
>
> Signed-off-by: Wei Yang
> ---
> Documentation/admin-guide/mm/memory-hotplug.rst | 40
>
16 matches
Mail list logo