Re: [libvirt PATCH 1/2] docs: virtiofs: move legacy docs to the bottom

2021-09-14 Thread Stefan Hajnoczi
On Thu, Sep 09, 2021 at 03:58:28PM +0100, Stefan Hajnoczi wrote: > A number of legacy issues make the virtiofs kbase article hard to > understand. Most users don't need to configure NUMA or a memory backend > other than memfd. Move that information to the bottom of the article so > the recommended

Re: [libvirt PATCH 1/2] docs: virtiofs: move legacy docs to the bottom

2021-09-09 Thread Ján Tomko
On a Thursday in 2021, Richard W.M. Jones wrote: On Thu, Sep 09, 2021 at 03:58:28PM +0100, Stefan Hajnoczi wrote: A number of legacy issues make the virtiofs kbase article hard to understand. Most users don't need to configure NUMA or a memory backend other than memfd. Move that information to

Re: [libvirt PATCH 1/2] docs: virtiofs: move legacy docs to the bottom

2021-09-09 Thread Richard W.M. Jones
On Thu, Sep 09, 2021 at 03:58:28PM +0100, Stefan Hajnoczi wrote: > A number of legacy issues make the virtiofs kbase article hard to > understand. Most users don't need to configure NUMA or a memory backend > other than memfd. Move that information to the bottom of the article so > the recommended

Re: [libvirt PATCH 1/2] docs: virtiofs: move legacy docs to the bottom

2021-09-09 Thread Ján Tomko
On a Thursday in 2021, Stefan Hajnoczi wrote: A number of legacy issues make the virtiofs kbase article hard to understand. Most users don't need to configure NUMA or a memory backend other than memfd. Move that information to the bottom of the article so the recommended syntax is most

[libvirt PATCH 1/2] docs: virtiofs: move legacy docs to the bottom

2021-09-09 Thread Stefan Hajnoczi
A number of legacy issues make the virtiofs kbase article hard to understand. Most users don't need to configure NUMA or a memory backend other than memfd. Move that information to the bottom of the article so the recommended syntax is most prominent. Suggested-by: Richard W.M. Jones