Socket receive, send
Hey Is there a good documentation on how messages are taking the tour from User calling read/write on socket fd, to kernel handling the actual send/receive functions? I wish to write code to capture the messages (no netfilter - I wish to bypass it) for processing. I know there is a socket->ops structure with functions pointers. I am at the point to look the inet version on that pointers. But if there is a documentation on this it will save me some time. Grzegorz.
On Tue, 14 Oct 2014 04:12:47 +0200, Grzegorz Dwornicki said:
Is there a good documentation on how messages are taking the tour from User calling read/write on socket fd, to kernel handling the actual send/receive functions? I wish to write code to capture the messages (no netfilter - I wish to bypass it) for processing.
Why do you wish to bypass netfilter? Is there a specific reason why you can't use a netfilter module, and avoid having to re-implement all the netfilter code? And what sort of processing do you need to do?
the best resource that _i_ know of (and probably you know it too) is http://www.linuxfoundation.org/collaborate/workgroups/networking/mainpage, see if that helps kind regards anupam On Tue, Oct 14, 2014 at 7:42 AM, Grzegorz Dwornicki <gd1100@gmail.com> wrote:
Hey
Is there a good documentation on how messages are taking the tour from User calling read/write on socket fd, to kernel handling the actual send/receive functions? I wish to write code to capture the messages (no netfilter - I wish to bypass it) for processing.
I know there is a socket->ops structure with functions pointers. I am at the point to look the inet version on that pointers. But if there is a documentation on this it will save me some time.
Grzegorz.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- In the beginning was the lambda, and the lambda was with Emacs, and Emacs was the lambda.
I did not know that page. Thx The reason why I wish to bypass the netfilter. Well there are two reasons. The main reason is that my project will connect to specific sockets and filtering the whole network flow by netfilter is a waste of cpu time. The second reason is no guarantee that netfilter guys will not change it once again into something else. This base socket implementation is there to stay a long time. Grzegorz. 14 paź 2014 06:38 "Anupam Kapoor" <anupam.kapoor@gmail.com> napisał(a):
the best resource that _i_ know of (and probably you know it too) is http://www.linuxfoundation.org/collaborate/workgroups/networking/mainpage, see if that helps
kind regards anupam
On Tue, Oct 14, 2014 at 7:42 AM, Grzegorz Dwornicki <gd1100@gmail.com> wrote:
Hey
Is there a good documentation on how messages are taking the tour from User calling read/write on socket fd, to kernel handling the actual send/receive functions? I wish to write code to capture the messages (no netfilter - I wish to bypass it) for processing.
I know there is a socket->ops structure with functions pointers. I am at the point to look the inet version on that pointers. But if there is a documentation on this it will save me some time.
Grzegorz.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-- In the beginning was the lambda, and the lambda was with Emacs, and Emacs was the lambda.
participants (3)
-
Anupam Kapoor -
Grzegorz Dwornicki -
Valdis.Kletnieks＠vt.edu