MºëÉ;¼<ôÃò
:Q8åkÙ±Â(Lì|T
jî½»6J|lÒ´õAÕ9Qªåp,es÷sê¨ëÆ,³3¡¥kVê9äz$1
§jn`zÚÃ-¥öP`ï¹è¶,öÈÃWHA?[ZG^C¨Ø-PÖaȤ;ñWk%_âKG£úE|
/Ý;ü3z| ¸©Tymyx7ãÊåAºO#ÙeF]D»uM/6ÏãPú3yà°Wb¤D>JÆØ
R§Ñj_¢ïQ×ä²7opé$´c%¶¶Û¥Ó×Böc½¸FB´Ó/§â±Ñé8uI¼¦#2ø¾mÌoTG¨
êÍØÂF.ê"·Å
Ë9ßDwH
¬Æ©Ùê¬
This Message was undeliverable due to the following reason:
Your message was not delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.
Most likely
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes
...to receive 2 regression fixes, 2 bug fixes for older issues, 2
fixes for new functionality added this cycle that have userspace ABI
concerns, and a small cleanup. These have appeared in a
On Thu, Mar 22, 2018 at 8:00 AM, David Sterba wrote:
> On Sat, Mar 10, 2018 at 10:19:04AM -0800, Andiry Xu wrote:
>> From: Andiry Xu
>>
>> Sysfs support allows user to get/post information of running NOVA instance.
>> After mount, NOVA creates four entries
On Thu, Mar 22, 2018 at 4:27 PM, Ross Zwisler
wrote:
> On Thu, Mar 22, 2018 at 03:47:01PM -0700, Dan Williams wrote:
>> On Thu, Mar 22, 2018 at 11:40 AM, Ross Zwisler
>> wrote:
>> > Instead of just failing to find namespaces when trying
On Thu, Mar 22, 2018 at 03:47:01PM -0700, Dan Williams wrote:
> On Thu, Mar 22, 2018 at 11:40 AM, Ross Zwisler
> wrote:
> > Instead of just failing to find namespaces when trying to filter by NUMA
> > node when CONFIG_NUMA wasn't enabled in the kernel, instead fail
> I've seen the response that peers directly below a Root Port could not
> DMA to each other through the Root Port because of the "route to self"
> issue, and I'm not disputing that.
Bjorn
You asked me for a reference to RTS in the PCIe specification. As luck would
have it I ended up in an
On Thu, Mar 22, 2018 at 11:40 AM, Ross Zwisler
wrote:
> Instead of just failing to find namespaces when trying to filter by NUMA
> node when CONFIG_NUMA wasn't enabled in the kernel, instead fail loudly as
> numactl does:
>
> # numactl --cpunodebind=0 ls
>
On Thu, Mar 22, 2018 at 11:40 AM, Ross Zwisler
wrote:
> commit 0a8dd795b4cf ("ndctl: removing daxctl io")
>
> didn't fully remove all daxctl io, leaving behind a few of the lines which
> were added by the original commit:
>
> commit 67b54c1c76e5 ("ndctl: daxctl:
On Wed, 2018-03-21 at 21:42 -0700, Dan Williams wrote:
> Per the ACPI specification the only functional purpose for a DIMM
> Control Region to be mapped into the system physical address space, from
> an OSPM perspective, is to support block-apertures. However, there are
> some BIOSen that publish
commit 0a8dd795b4cf ("ndctl: removing daxctl io")
didn't fully remove all daxctl io, leaving behind a few of the lines which
were added by the original commit:
commit 67b54c1c76e5 ("ndctl: daxctl: Adding io option for daxctl")
Signed-off-by: Ross Zwisler
Cc: Dave
Instead of just failing to find namespaces when trying to filter by NUMA
node when CONFIG_NUMA wasn't enabled in the kernel, instead fail loudly as
numactl does:
# numactl --cpunodebind=0 ls
numactl: This system does not support NUMA policy
Signed-off-by: Ross Zwisler
gcc 7.3.1 provides the following warning when compiling numastat.c:
numastat.c: In function ‘add_pids_from_pattern_search’:
numastat.c:1316:41: warning: ‘%s’ directive output may be truncated writing
up to 255 bytes into a region of size 58 [-Wformat-truncation=]
snprintf(fname, sizeof(fname),
gcc 7.3.1 provides the following warning when compiling affinity.c:
affinity.c: In function ‘affinity_file’:
affinity.c:158:2: warning: ‘readdir_r’ is deprecated [-Wdeprecated-declarations]
while (readdir_r(dir, , ) == 0 && dep) {
^
In file included from affinity.c:39:0:
This is needed so that other projects can add a dependency on libnuma via
PKG_CHECK_MODULES([NUMA], [numa]). This enabling makes 'make install' do
the right thing, and of course individual distros will need to add enabling
to their associated packages (rpm, deb, etc.) so the package manager
On Thu, Mar 22, 2018 at 11:26 AM, Dave Jiang wrote:
> The FW_START DSM should have input/out of 0/8, the code incorrectly
> is passing in 4/4. This is causing failure with newer BIOS that check
> the input/output parameters more strictly.
>
> Signed-off-by: Dave Jiang
The FW_START DSM should have input/out of 0/8, the code incorrectly
is passing in 4/4. This is causing failure with newer BIOS that check
the input/output parameters more strictly.
Signed-off-by: Dave Jiang
---
ndctl/lib/intel.c |4 ++--
1 file changed, 2
On Thu, Mar 22, 2018 at 09:28:11AM -0700, Dan Williams wrote:
> I can switch to the for() loop model, but it isn't 'done' flag, it's a
> 'retry' flag. I.e. if xfs_break_leased_layouts() dropped
> XFS_MMAPLOCK_EXCL we need to retry xfs_break_dax_layouts(), and if
Oh, indeed.
>
3955639556
00:31:20---Çë ²é ÔÄ ¸½ ¼þ ÄÚ ÈÝ
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
On Thu, Mar 22, 2018 at 12:43 AM, Christoph Hellwig wrote:
> On Wed, Mar 21, 2018 at 03:58:31PM -0700, Dan Williams wrote:
>> xfs_break_dax_layouts(), similar to xfs_break_leased_layouts(), scans
>> for busy / pinned dax pages and waits for those pages to go idle before
>> any
On Thu, Mar 22, 2018 at 12:27 AM, Christoph Hellwig wrote:
>> + ASSERT(xfs_isilocked(ip, XFS_IOLOCK_SHARED | XFS_IOLOCK_EXCL
>> + | (reason == BREAK_UNMAPI
>> + ? XFS_MMAPLOCK_EXCL : 0)));
>
> please split the
On Sat, Mar 10, 2018 at 10:19:04AM -0800, Andiry Xu wrote:
> From: Andiry Xu
>
> Sysfs support allows user to get/post information of running NOVA instance.
> After mount, NOVA creates four entries under proc directory
> /proc/fs/nova/pmem#/:
>
> timing_stats IO_stats
Looks good,
Reviewed-by: Christoph Hellwig
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
Looks good,
Reviewed-by: Christoph Hellwig
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
On Wed, Mar 21, 2018 at 03:58:31PM -0700, Dan Williams wrote:
> xfs_break_dax_layouts(), similar to xfs_break_leased_layouts(), scans
> for busy / pinned dax pages and waits for those pages to go idle before
> any potential extent unmap operation.
>
> dax_layout_busy_page() handles synchronizing
> + ASSERT(xfs_isilocked(ip, XFS_IOLOCK_SHARED | XFS_IOLOCK_EXCL
> + | (reason == BREAK_UNMAPI
> + ? XFS_MMAPLOCK_EXCL : 0)));
please split the assert, e.g.:
ASSERT(xfs_isilocked(ip, XFS_IOLOCK_SHARED |
Looks good,
Reviewed-by: Christoph Hellwig
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
27 matches
Mail list logo