Port to Thread Mapping

Question

2.50/5 (2 votes)

See more:

Hi,

I need help for problem port to thread mapping, for example, a process have 2 threads (T1, T2)and one thread(T1) is using port x and another(T2) is using port y. Now here is the problem, how to find that which thread is using which port. Based on example, T1 -> x, T2 -> y here. I have Process ID and port number only. Solution can be in user mode or kernel but I am looking for optimized approach.

Here is my doubt - To access any port, I need to bind a socket to any unique port. Now application creates a socket object, get handle and send/receive data to/from port. While this thread is using this port none can get access to this port and no-one can get handle for this socket object. That means at a particular time only 1 thread can have socket handle and use specific port. So now in my example 2 threads are using the same scenario, My question is how to identify which thread is using which port ?

I am thinking to parse process handle table and check object attribute but I don't know how to write it in code.

For my curiosity, how is a packet transferred from the port to thread ? Any article or referrer would be appreciated.

Apart from above doubt I have some more -
1. How is it managed by OS network part ?
2. Why do I need to create a socket ? Why can't I directly send or receive data to/from any port ?
3. How is a data packet read by thread belongs to multi-Threaded process ?
4. Is it possible for a thread can perform any operation on same port which is being used by another thread belongs to the same process?

Thanks,
Subrat Sarkar

Posted 28-Aug-12 19:15pm

SubratSarkar

Updated 30-Aug-12 21:06pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

pasztorpisti · Answer 1 · 2012-08-28T21:11:00

Any threads can use any of the sockets inside a process. I can easily pass data to a socket from 2 threads interchangeably. I don't know the internals of current windows versions but I guess there is no such data stored for sockets. Probably there is only a lock (or maybe lockless data structure) to synchronize between multiple threads that try to access the same socket at the same time and that's it.

EDIT: In high performance network engines often a thread pool is used to serve sockets when an event occurs (incoming data available, or free space is available in the send buffer, incoming connection, ...) with one of the sockets and something has to be done with the sockets, each time a random thread is used as a servant so finding out which thread handles the socket just makes no sense, its often random.

SubratSarkar wrote:
For my curiosity, how is a packet transferred from the port to thread ? Any article or referrer would be appreciated.

When the packet comes in on your ethernet card its header is parsed. If the target address isn't your machine then the packet is routed (if your machine is configured that way). If the target address is your machine then according to the target port number the incoming data is stored in the receive buffer (size of receive buffer is configurable with setsockopt/SO_RCVBUF) of the socket object inside the OS identified by the port.
Many processes can have an open handle that reference the same socket object in the OS, and any thread of these processes that application can read out data from the receive buffer of the socket to the address space of the app. I myself never used a socket object from more than one processes but there is a function to duplicate socket handles: WSADuplicateSocket[^].

Summary: The address/port pair in the incoming packet identifies a machine(address) and a socket object inside (port) the networking part of the OS. Any application can have an open handle to that socket object (the handle is basically a process-local "reference counting pointer" to an object inside the OS) and any thread inside those applications can manipulate the socket object. When all applications close all handles to the socket object it might still remain alive for some time if it has data to send in its send buffer (search for socket linger to learn more about this) or unfinished tasks regarding the TCP protocol (shutdown, etc...).