Re: RFD: Limiting scope of ep_ memory

[Evan Huus <eapache () gmail com>]

On Mon, Oct 22, 2012 at 6:22 PM, Evan Huus <eapache () gmail com> wrote:
> On Mon, Oct 22, 2012 at 5:36 PM, Jakub Zawadzki
> <darkjames-ws () darkjames pl> wrote:
> > On Mon, Oct 22, 2012 at 12:43:49PM -0400, Evan Huus wrote:
> > > Perhaps pinfo should have its own scope that is between ep and
> > > se? This would be much easier given the changes suggested in [1].
> > >
> > > [1] https://www.wireshark.org/lists/wireshark-dev/201210/msg00178.html
> >
> > Evan, when do you plan to merge it?
>
> Well, I've had absolutely zero feedback on it so far, so I'm not sure
> if that's a good sign or a bad one...
>
> I was planning on taking it slow, maybe merging it this weekend if
> nobody raised any objections. I can merge it basically right now
> though if you can use it - since it doesn't touch any existing code
> it's not that disruptive. I just didn't want to merge it before the
> general design had gotten a couple of acks on the list, since API
> changes after it's in use are a pain.

The stuff that works has been merged in revision 45746. It should be
usable for what you need in pinfo. There's lots more to do before its
ready to replace emem in the general case though.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe