> >> >> > +\subsubsection{ Workload specific mapping}\label{sec:Device Types / PMEM Device / Possible Security Implications / Countermeasures / Workload}
> >> >> > +For SHARED mappings, for the workload is a single application inside
> >> >> > +the driver and there is no risk in sharing data. Device sharing
> >> >>
> >> >> Sorry for noticing this only now, but I have trouble parsing this
> >> >> sentence. Does it mean that you can use SHARED mapping if the workload
> >> >> is a single application?
> >> >
> >> > yes and if risk in sharing data is very less or acceptable.
> >> >
> >> >>
> >> >> > +same backing region with SHARED mapping can be used as a valid configuration.
> >>
> >> Hm... maybe rephrase this paragraph as:
> >>
> >> "When using SHARED mappings with a workload that is a single application
> >> inside the driver where the risk in sharing data is very low or
> >> nonexisting, the device sharing the same backing region with a SHARED
> >> mapping can be used as a valid configuration."
> >
> > Thank you Cornelia!
> > I tried to reread my initial statement and I think that also precisely conveys
> > the use-case.
> >
> > If you are okay, I will respin v6 with only space with bracket change
> > and Stefan r-o-b?
>
> And my proposed change? If nobody else has a comment, I think we could
> start voting on that.
Sure.
Thanks,
Pankaj
>
