From: Andi Kleen <ak@suse.de>
To: "Gary Chan" <hpchan5@ie.cuhk.edu.hk>
Cc: netdev@vger.kernel.org
Subject: Re: Linux UDP Implementation
Date: Sat, 2 Sep 2006 13:42:21 +0200 [thread overview]
Message-ID: <200609021342.21345.ak@suse.de> (raw)
In-Reply-To: <00f401c6ccc2$40ad2a90$193aa8c0@mclabhpchan5>
> It seems that the implementation (at code level) does not match with the
> actual behaviour. I would like to seek expertise on clarifying my
> understanding in UDP implementation so that this phenomenon can be
> explained.
How about you just add some printks or use a tool like systemtap to instrument
the code path? That should give some insights what is actually going on.
-Andi
--
VGER BF report: U 0.473534
prev parent reply other threads:[~2006-09-02 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 5:56 Linux UDP Implementation Gary Chan
[not found] ` <44F715B5.5070905@hp.com>
2006-09-02 6:27 ` Gary Chan
2006-09-02 11:42 ` Andi Kleen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200609021342.21345.ak@suse.de \
--to=ak@suse.de \
--cc=hpchan5@ie.cuhk.edu.hk \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.