Re: [ndctl PATCH 4/5] ndctl: Make new interfaces to get information by Physical Address

On Tue, Sep 5, 2017 at 7:21 PM, Yasunori Goto wrote: > > On Fri, Sep 1, 2017 at 6:21 AM, Yasunori Goto > wrote: > > > > > > This patch makes new interfaces : > > > - Confirm NFIT command is supported or not. (nfit.c) > > > - Call translate SPA

Re: [ndctl PATCH 4/5] ndctl: Make new interfaces to get information by Physical Address

> On Tue, Sep 5, 2017 at 7:21 PM, Yasunori Goto wrote: > > > > On Fri, Sep 1, 2017 at 6:21 AM, Yasunori Goto > > wrote: > > > > > > > > This patch makes new interfaces : > > > > - Confirm NFIT command is supported or not. (nfit.c) > > > > - Call

Mail System Error - Returned Mail

The original message was received at Wed, 6 Sep 2017 11:11:23 +0800 from lists.01.org [48.230.189.126] - The following addresses had permanent fatal errors - ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org

Re: [RFC patch 0/4]ndctl: nvdimmd: notify/monitor the feathers of over threshold event

[ adding Song ] Song, I'm adding you to this thread for an opinion on what makes hardware monitoring tooling easier to consume in a production environment. QI is writing a daemon to catch alarms and notifications from the kernel's nvdimm sub-system. QI, Song presented on extending SCSI uevents

Re: [ndctl PATCH 1/5] ndctl: Introduce libndctl-nfit.h

On Tue, Sep 5, 2017 at 11:13 AM, Dan Williams wrote: > On Fri, Sep 1, 2017 at 6:16 AM, Yasunori Goto > wrote: > > > > This patch introduces libndctl-nfit.h. > > > > Since these command can be executed via ND_CMD_CALL, > > libndctl.h which is

[PATCH] libnvdimm, btt: clean up warning and error messages

Convert all WARN* style messages to dev_WARN, and for errors in the IO paths, use dev_err_ratelimited. Also remove some BUG_ONs in the IO path and replace them with the above - no need to crash the machine in case of an unaligned IO. Cc: Dan Williams Signed-off-by:

Re: [RFC patch 0/4]ndctl: nvdimmd: notify/monitor the feathers of over threshold event

For that, I would say generating JSON format is a solid building block. In my setup, I have use Scribe https://en.wikipedia.org/wiki/Scribe_(log_server) . And further processing of data happens after that. But I don't think Scribe is available everywhere. Besides SCSI events, JSON format is

[PATCH 4/9] ext4: add ext4_should_use_dax()

This helper, in the spirit of ext4_should_dioread_nolock() et al., replaces the complex conditional in ext4_set_inode_flags() and will soon be called in multiple places. Signed-off-by: Ross Zwisler --- fs/ext4/ext4_jbd2.h | 15 +++ fs/ext4/inode.c |

[PATCH 5/9] ext4: ext4_change_inode_journal_flag error handling

Rework the error handling in ext4_change_inode_journal_flag() so that multiple paths can re-use portions of the same cleanup code via gotos instead of each path doing their own cleanup. This will benefit later patches that add more paths to this function that must be unwound on error.

[PATCH 9/9] ext4: add per-inode DAX flag

Follow the lead of XFS and add a per-inode flag that allows the choice of whether or not to use DAX to be made for individual files. As with XFS this flag can also be set on a directory, in which case it will be inherited by new inodes (both subdirectories and files) created within that

[PATCH 7/9] ext4: prevent data corruption with inline data + DAX

If an inode has inline data it is currently prevented from using DAX by a check in ext4_should_use_dax(). When the inode grows inline data via ext4_create_inline_data() or removes its inline data via ext4_destroy_inline_data_nolock(), the value of S_DAX can change. Currently these changes are

[PATCH 3/9] xfs: validate bdev support for DAX inode flag

Currently only the blocksize is checked, but we should really be calling bdev_dax_supported() which also tests to make sure we can get a struct dax_device and that the dax_direct_access() path is working. This is the same check that we do for the "-o dax" mount option in xfs_fs_fill_super().

[PATCH 6/9] ext4: safely transition S_DAX on journaling changes

The IOCTL path which switches the journaling mode for an inode is currently unsafe because it doesn't properly do a writeback and invalidation on the inode. In XFS, for example, safe transitions of S_DAX are handled by xfs_ioctl_setattr_dax_invalidate() which locks out page faults and I/O, does a

[PATCH 8/9] ext4: add sanity check for encryption + DAX

We prevent DAX from being used on inodes which are using ext4's built in encryption via a check in ext4_should_use_dax(). We do have what appears to be an unsafe transition of S_DAX in ext4_set_context(), though, where S_DAX can get disabled without us doing a proper writeback + invalidate. I

[PATCH 1/9] ext4: remove duplicate extended attributes defs

The following commit: commit 9b7365fc1c82 ("ext4: add FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR interface support") added several defines related to extended attributes to ext4.h. They were added within an #ifndef FS_IOC_FSGETXATTR block with the comment: /* Until the uapi changes get merged for

[PATCH 0/9] add ext4 per-inode DAX flag

The original intent of this series was to add a per-inode DAX flag to ext4 so that it would be consistent with XFS. In my travels I found and fixed several related issues in both ext4 and XFS. I'm not fully happy with the ways that ext4 DAX interacts with conflicting features (journaling, inline

[PATCH 2/9] xfs: always use DAX if mount option is used

The current code has an issue where the user can't reliably tell whether or not DAX is being used to service page faults and I/O when the DAX mount option is used. In this case each inode within the mounted filesystem starts with S_DAX set due to the mount option, but it can be cleared if someone

Re: [PATCH 0/9] add ext4 per-inode DAX flag

On 9/5/17 5:35 PM, Ross Zwisler wrote: > The original intent of this series was to add a per-inode DAX flag to ext4 > so that it would be consistent with XFS. In my travels I found and fixed > several related issues in both ext4 and XFS. Hi Ross - hch had a lot of reasons to nuke the dax flag

Re: [RFC patch 0/4]ndctl: nvdimmd: notify/monitor the feathers of over threshold event

Hi Dan, Thanks for adding me to the thread. Hi QI, I am not familiar with the NVDIMM code, so my experiences may not apply well to your case. We have done multiple designs to capture SCSI sense code in a log. The first thing we learnt is do NOT use kernel debug messages (dmesg). The dmesg

Re: [RFC patch 0/4]ndctl: nvdimmd: notify/monitor the feathers of over threshold event

On Tue, Sep 5, 2017 at 4:10 PM, Song Liu wrote: > Hi Dan, > > Thanks for adding me to the thread. > > Hi QI, > > I am not familiar with the NVDIMM code, so my experiences may not apply > well > to your case. > > We have done multiple designs to capture SCSI sense code in a

Re: [RFC patch 0/4]ndctl: nvdimmd: notify/monitor the feathers of over threshold event

On Tue, Sep 5, 2017 at 5:02 PM, Song Liu wrote: > For that, I would say generating JSON format is a solid building block. In > my > setup, I have use Scribe https://en.wikipedia.org/wiki/Scribe_(log_server) > . > And further processing of data happens after that. But I

Re: [ndctl PATCH 1/5] ndctl: Introduce libndctl-nfit.h

> Actually, since there's some other fixups needed on this series, I'll let > you resend this with the "attribute packed" statements added back in. I'll > follow on later with kernel and ndctl patches to remove the ones that are > not needed. Hmm, since I may still misunderstand yet, let me

Re: [ndctl PATCH 1/5] ndctl: Introduce libndctl-nfit.h

On Tue, Sep 5, 2017 at 6:28 PM, Yasunori Goto wrote: > > Actually, since there's some other fixups needed on this series, I'll let > > you resend this with the "attribute packed" statements added back in. > I'll > > follow on later with kernel and ndctl patches to remove

Re: [ndctl PATCH 4/5] ndctl: Make new interfaces to get information by Physical Address

> On Fri, Sep 1, 2017 at 6:21 AM, Yasunori Goto wrote: > > > > This patch makes new interfaces : > > - Confirm NFIT command is supported or not. (nfit.c) > > - Call translate SPA featture of ACPI 6.2. (nfit.c) > > - Find region by System Physical Address (libndctl.c)

规避合伙人风险的4种方法

01:39:07 ·¢¼þÈË: ÕŊüÎá ·¢ËÍʱ¼ä: 2017-09-06 01:39:07 ÊÕ¼þÈË: 'linux-nvdimm'; linux-nvdimm@lists.01.org Ö÷Ìâ: 894448944489444 ¸½ ¼þ ²é ÔÄ ´ó ¸Ù ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org

完成销-售目标有哪41种方法？

ת·¢ÓʼþÐÅÏ¢ ·¢¼þÈË: ÁΗåÃ÷ ·¢ËÍʱ¼ä: 2017-09-06 01:17:05 ÊÕ¼þÈË: 'linux-nvdimm'; linux-nvdimm@lists.01.org Ö÷Ìâ: 89440 89440 ¸½ ¼þ ²é ÔÄ ´ó ¸Ù 89440 ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org

构建适合自己公司的预算管理体系

ת·¢ÓʼþÐÅÏ¢ ·¢¼þÈË: ºú–OÃë ·¢ËÍʱ¼ä: 2017-09-06 01:07:07 ÊÕ¼þÈË: 'linux-nvdimm'; linux-nvdimm@lists.01.org Ö÷Ìâ: 894388943889438¸½ ¼þ ²é ÔÄ ´ó ¸Ù ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org

Re: [ndctl PATCH 1/5] ndctl: Introduce libndctl-nfit.h

On Fri, Sep 1, 2017 at 6:16 AM, Yasunori Goto wrote: > > This patch introduces libndctl-nfit.h. > > Since these command can be executed via ND_CMD_CALL, > libndctl.h which is shared between ndctl command and kernel does not > have to include these defintions. > > So,

Re: [ndctl PATCH 2/5] ndctl: make interface to read device/nfit/dsm_mask

On Fri, Sep 1, 2017 at 6:17 AM, Yasunori Goto wrote: > > To check what feature can be called via ND_CMD_CALL, ndctl need to read > device/nfit/dsm_mask. > Since direct pointer access is not permitted, > ndctl_bus_get_nfit_dsm_mask() is created to access nfit_dsm_mask. > It

Re: [ndctl PATCH 4/5] ndctl: Make new interfaces to get information by Physical Address

On Fri, Sep 1, 2017 at 6:21 AM, Yasunori Goto wrote: > > This patch makes new interfaces : > - Confirm NFIT command is supported or not. (nfit.c) > - Call translate SPA featture of ACPI 6.2. (nfit.c) > - Find region by System Physical Address (libndctl.c) > - Find

●●●●澳門新葡京-註冊送38-領取釦釦：746529854-［鐵板精準資料］●●●●

___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm