Message ID | 20190503213231.12280-1-vishal.l.verma@intel.com (mailing list archive) |
---|---|
Headers | show |
Series | daxctl: add a new reconfigure-device command | expand |
This all looks quite nice to me. Thanks, Vishal! One minor nit: for those of us new to daxctl and friends, they can be a bit hard to get started with. Could you maybe add a few example invocations to the Documentation, or even this cover letter to help us newbies get started?
On Mon, 2019-05-06 at 14:50 -0700, Dave Hansen wrote: > This all looks quite nice to me. Thanks, Vishal! > > One minor nit: for those of us new to daxctl and friends, they can be > a > bit hard to get started with. Could you maybe add a few example > invocations to the Documentation, or even this cover letter to help us > newbies get started? Yes, good idea, I'll add an examples section to the Documentation page (other commands do this, and this should too), and add those to the cover letter as well for v2. Thanks! -Vishal
On Mon, 2019-05-06 at 22:14 +0000, Verma, Vishal L wrote: > On Mon, 2019-05-06 at 14:50 -0700, Dave Hansen wrote: > > This all looks quite nice to me. Thanks, Vishal! > > > > One minor nit: for those of us new to daxctl and friends, they can > > be > > a > > bit hard to get started with. Could you maybe add a few example > > invocations to the Documentation, or even this cover letter to help > > us > > newbies get started? > > Yes, good idea, I'll add an examples section to the Documentation page > (other commands do this, and this should too), and add those to the > cover letter as well for v2. I meant to add, for now, a few of the most useful invocations probably look like: 1. # daxctl reconfigure-device --mode=system-ram dax0.0 (this will also online the memory sections) 2. # daxctl reconfigure-device --mode=system-ram --no-online dax0.0 (this will *not* online the memory sections) 3. # daxctl reconfigure-device --mode=devdax --attempt-offline dax0.0 (this requires Pavel's patches for kmem-unbind, and won't work with vanilla v5.1)