> -----Original Message----- > From: Burakov, Anatoly > Sent: Tuesday, June 26, 2018 9:21 PM > To: Zhang, Qi Z <[email protected]>; [email protected] > Cc: Ananyev, Konstantin <[email protected]>; [email protected]; > Richardson, Bruce <[email protected]>; Yigit, Ferruh > <[email protected]>; Shelton, Benjamin H > <[email protected]>; Vangati, Narender > <[email protected]> > Subject: Re: [PATCH v4 06/24] ethdev: enable hotplug on multi-process > > On 26-Jun-18 1:58 PM, Zhang, Qi Z wrote: > > > > my understand is peer is identified by a string (or filename) what I > > mean is clone the content of the buffer that peer point to , So I > > don't need to worry if the original peer be used to point to some > > other data > > > > As far as the application is concerned, peer is an opaque pointer, and should > be treated as such. Peeking behind a void pointer that is not designed for > this > purpose is not a good idea, even if technically you know what's in there.
We can expose a clone interface, like MP_PEER_CLONE, so we don't need to know what's inside, just need to know that it can be used on another thread? > > -- > Thanks, > Anatoly
