Speed up trace mode (GSoC Project)

[Mihir Luthra]

Hi,

I had a few questions regarding Darwin trace library.

Darwintrace library being injected, most I/O operations get reimplemented.
If a “single” process is working on files, it more or less should call most
of these functions again and again.
Like that particular process may call open, rename, rmdir etc.
So lets say a process was allowed to open file “X”. (closed it too)
The same process has to do rmdir now. So it will again call
__darwintrace_is_in_sandbox().
If a file has already been checked once, that file path can be stored at a
place so that all these checks don’t need to be re-performed
and next time if the same process is calling any of these functions, it
doesn’t need to call the time taking __darwintrace_is_in_sandbox() and
should check that list of already checked files first.
This should optimise the trace mode to some extent.
Is that right or am I mistaken somewhere?


On Sun, Mar 24, 2019 at 12:22 AM Mihir Luthra <1999mihir.luthra at gmail.com>
wrote:

> Hi,
>
> I wanted to contribute to the MacPorts documentation.
> The guide says that it currently is in docboook format with work in
> progress to change it to adoc.
> Actually I got a bit confused with this.
> Where exactly should I add a file in order to create a new section?
> Like currently there are 7 sections in MacPorts documentation.
>
> I was thinking to add an 8th section which gives a small high level tour
> of the codebase to a newcomer joining the community.
> I personally would only be able to give tour of trace mode, but that
> section can be populated with other topics as well later.
>
> Mojca, I will stick to this email thread for any further communications
> Apologies for previously creating many!
>
> Regards
>
> -Mihir
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20190324/9620548a/attachment.html>