> -----Original Message----- > From: Maxime Coquelin [mailto:maxime.coque...@redhat.com] > Sent: Thursday, February 22, 2018 8:33 PM > To: Tan, Jianfeng; email@example.com > Cc: y...@fridaylinux.org > Subject: Re: [PATCH 4/4] vhost: avoid populate guest memory > > > >> What could be done is maybe to have an EAL API for mmaping, with an > >> associated EAL parameter to state whether it want populating or not. > >> This option would be disabled by default. > >> > >> Does that sounds reasonable? > > > > If we look for an application-level configuration, it's not necessary to > > have > such a parameter. Refer to the 3rd patch in this series, if we make all > (current/future) memory locked, the mmap() syscall will populate the > memory. > > OK, but in that case it should be documented. > I see OVS has also a parameter to request the memory to be locked, but > it seems not to be the default, so the user could face a change in the > behavior it didn't expect.
Make sense, will send v2 with the note. Thanks, Jianfeng