The current implementation of acpi_parse_entries_array() assumes that each
subtable has a standard ACPI subtable entry of type struct
acpi_subtable_header. This standard subtable header has a one byte length
followed by a one byte type.
The HMAT subtables have to allow for a longer length so
Add a new sysfs subsystem, /sys/devices/system/hmat, which surfaces
information about memory initiators and memory targets to the user. These
initiators and targets are described by the ACPI SRAT and HMAT tables.
A "memory initiator" in this case is a NUMA node containing one or more
devices
This is the third revision of my patches adding a sysfs representation
of the ACPI Heterogeneous Memory Attribute Table (HMAT). These patches
are based on v4.15-rc3 and a working tree can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/linux.git/log/?h=hmat_v3
My goal is
Add performance information found in the HMAT to the sysfs representation.
This information lives as an attribute group named "local_init" in the
memory target:
# tree mem_tgt2
mem_tgt2
├── firmware_id
├── is_cached
├── local_init
│ ├── mem_init0 -> ../../mem_init0
│ ├──
On Wed, 2017-12-13 at 16:33 -0500, Jeff Moyer wrote:
> Hi,
>
> When a sector mode namespace is initially created, the arena's
> err_lock
> is not initialized. If, on the other hand, the namespace already
> exists, the mutex is initialized. To fix the issue, I moved the
> mutex
> initialization
Hi,
When a sector mode namespace is initially created, the arena's err_lock
is not initialized. If, on the other hand, the namespace already
exists, the mutex is initialized. To fix the issue, I moved the mutex
initialization into the arena_alloc, which is called by both
discover_arenas and
¸½ ¼þ Ïê ÔÄ
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
On Tue, Dec 05, 2017 at 04:56:48PM -0700, Ross Zwisler wrote:
> This is the second revision of my MAP_SYNC + dm-log-writes support for
> xfsprogs.
Friendly ping on this xfsprogs series.
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
有效调岗调薪、裁员解雇及违纪问题员工处理技巧
2017年12月15--16日-广州
2017年12月18--19日-上海
2017年12月22--23日-深圳
2017年12月29--30日-北京
━
【学员对象】董事长、总经理、副总经理、人力资源总监/经理/专员及人事行政管理人员、工会干部、法务人员及相关管理人员、相关律师等。
【费用】3200元/1人
━
●培-训-报-名-中-心:
Michal Hocko writes:
> On Thu 07-12-17 19:30:55, Dan Williams wrote:
>> When device-dax is operating in huge-page mode we want it to behave like
>> hugetlbfs and report the MMU page mapping size that is being enforced by
>> the vma. Similar to commit 31383c6865a5 "mm,
Hello,
these two patches fix handling of ENOSPC during DAX faults. The problem is
that currently running transaction may be holding lots of already freed
blocks which can be reallocated only once the transaction commits. Standard
retry logic in ext4_iomap_end() does not work for DAX page fault
Ext4 needs to pass through error from its iomap handler to the page
fault handler so that it can properly detect ENOSPC and force
transaction commit and retry the fault (and block allocation). Add
argument to dax_iomap_fault() for passing such error.
Signed-off-by: Jan Kara
---
When allocation of underlying block for a page fault fails, we fail the
fault with SIGBUS. However we may well hit ENOSPC just due to lots of
free blocks being held by the running / committing transaction. So
propagate the error from ext4_iomap_begin() and implement do standard
allocation retry
13 matches
Mail list logo