Re: [PATCH v2 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

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

[PATCH v2 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

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

[PATCH v2 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

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

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

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

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

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

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

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

[PATCH v1 8/9] drm/doc: Add initial komeda driver documentation

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

[PATCH v1 8/9] drm/doc: Add initial komeda driver documentation

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

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

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 >> *

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

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

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

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

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

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 >> --- >>

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

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

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

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 > >

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

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

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

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 >