On Thu, Nov 1, 2018 at 2:28 PM Burakov, Anatoly <[email protected]> wrote:
> On 01-Nov-18 1:39 PM, Alejandro Lucero wrote: > > > > > > On Thu, Nov 1, 2018 at 10:40 AM Burakov, Anatoly > > <[email protected] <mailto:[email protected]>> wrote: > > > > On 31-Oct-18 5:29 PM, Alejandro Lucero wrote: > > > If a device reports addressing limitations through a dma mask, > > > the IOVAs for mapped memory needs to be checked out for ensuring > > > correct functionality. > > > > > > Previous patches introduced this DMA check for main memory code > > > currently being used but other options like legacy memory and the > > > no hugepages one need to be also considered. > > > > > > This patch adds the DMA check for those cases. > > > > > > Signed-off-by: Alejandro Lucero <[email protected] > > <mailto:[email protected]>> > > > --- > > > > IMO this needs to be integrated with patch 5. > > > > > > Not sure about this. patch 5 is a follow-up of patch 4, and this is to > > add support for other EAL supported memory options. > > > > So it's a followup of patch 5, adding pretty much the same functionality > (only in a different place). It's pretty safe to say these should be in > the same patch, or at the very least one after the other. > > Ok. I'll do so. Thanks > -- > Thanks, > Anatoly >
