Hi,
If the object is
> in optimizing code using data structures
In what way to make it run faster? Wiresharks innards are quite complicated and 
may take a while to get the hang of but if it would be possible
To optimize in terms of memory usage or execution speed it would be very 
beneficial for the performance.

-          The packet list handling /ui/qt/ packet_list.cpp would be the place 
to start

-          Reassembly (epan/reassembly.c)

-          Conversations(hastable sizes and lookup) (epan/conversations.c)

-          Epan/proto.c
You’d probably need a large capture file and run profiling on it to find the 
hot spots which may vary depending on the protocol mix in the capture and
Whether the GUI version (Wirsehark) or the cl version ( tshark) are used and if 
filters are applied or not.

Regards
Anders

From: [email protected] 
[mailto:[email protected]] On Behalf Of Breanna 
Devore-McDonald
Sent: den 8 september 2015 09:12
To: [email protected]
Subject: [Wireshark-dev] Greetings and Where to Start

Hello,

My name is Breanna and I am a junior Computer Science/ Cyber Security undergrad 
at the University of Notre Dame. I am currently in a Data Structures course 
which requires me to find an interesting open-source project to *hopefully* 
contribute to, using the knowledge I should gain throughout the semester in 
optimizing code using data structures. I recently heard of Wireshark through my 
Computer Networks course and I am very interested and would love to find a way 
to contribute. However, I have no idea where to start. Do you think there's any 
place in the Wireshark code where I could help? (Or maybe, if it seems 
Wireshark is not the right fit for me, do you know of any projects that could 
fit?)

Any help would be greatly appreciated!
-Breanna

--
Breanna DeVore-McDonald
University of Notre Dame '17
Computer Science
[email protected]<mailto:[email protected]>
530-276-4805
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to