Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Ethereal-dev: Re: [Ethereal-dev] Where is the memory consumed ?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date: Thu, 9 Sep 2004 13:29:49 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I had this same problem, so I wrote a patch, which I will have to dig
up, that would change the output writing in tethereal to change to a
NON blocking mode. This prevented back log, and it simply would continue
sending data at the pipe without waiting. Some packets could obviously
be lost but it was not a problem.

On Thu, 09 Sep 2004 12:07:32 -0700 Pierre JUHEN <pierre.juhen@xxxxxxxxxx>
wrote:
>I am looking for the way to implement an option in tethereal, that
>would
>regularly sweep the memory, when
>tethereal write to a pipe.
>
>The option woud permit to sweep the memory use by packets that are
>"old"
>(more than x seconds, typically 300/600),
>such a way the dissectors have a big enough "backlog" to work, ant
>>
>ethereal would be able to run for a very long time,
>eventually forever ?
>
>I read the ring buffer code to find out how the memory is cleaned
>in
>that case.
>
>Question :
>
>    Where is the memory useb by the packets ?
>       on the capture side ?
>       on the wtap_dump side ?
>
>    Behing which varaible / pointer ?
>
>Thank you.
>
>Regards,
>
>Pierre Juhen
>
>
>_______________________________________________
>Ethereal-dev mailing list
>Ethereal-dev@xxxxxxxxxxxx
>http://www.ethereal.com/mailman/listinfo/ethereal-dev
-----BEGIN PGP SIGNATURE-----
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 2.4

wkYEARECAAYFAkFAvqIACgkQFh/Ot+gyoF7MwQCfXGAkj8/p2kTrAXqBccfr/Oy+11MA
n0O1fYsI2y92BSDRcoWi9MY1rxhn
=HGcK
-----END PGP SIGNATURE-----