Date: Sun, 26 Mar 2006 19:51:45 -0800 From: "Jin Guojun [VFFS]" <g_jin@lbl.gov> To: OxY <oxy@field.hu> Cc: Lucas Holt <luke@foolishgames.com>, FreeBSD Mailing Lists <freebsd-performance@freebsd.org>, Arne Woerner <arne_woerner@yahoo.com> Subject: Re: packet drop with intel gigabit / marwell gigabit Message-ID: <44276151.1060302@lbl.gov> In-Reply-To: <008501c65030$96726710$0201a8c0@oxy> References: <20060322071023.70808.qmail@web30305.mail.mud.yahoo.com> <442187FE.3060300@lbl.gov> <003301c64f44$89fdcd40$0201a8c0@oxy> <820F5FD6-C31F-4C28-9E66-64643C03086B@foolishgames.com> <4424520D.9000504@lbl.gov> <008501c65030$96726710$0201a8c0@oxy>
next in thread | previous in thread | raw e-mail | index | archive | help
OxY wrote:
> what kind of details should i attach? to analyze the problem?
Assume that you have process A to cause process B dropping packets:
Step (1):
Run B only -- what is the maximum through without packet drop?
what is the CPU utilization?
what type of traffic (protocol -- TCP, UDP, etc.)
does B use?
does B have other I/O? If so, how much is the I/O
bandwidth used?
Step (2):
reRun B and involving A gradually (increasing A's wieght) till B drops
packets.
provide all above statistics for A and B at this point (where drop
starts).
One thing I missed in your original post what protocol drops packet --
TCP or UDP?
-Jin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44276151.1060302>
