All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Chapman <jchapman@katalix.com>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: L F <lfabio.linux@gmail.com>, netdev@vger.kernel.org
Subject: Re: e1000 driver and samba
Date: Sun, 16 Sep 2007 17:24:15 +0100	[thread overview]
Message-ID: <46ED58AF.1070000@katalix.com> (raw)
In-Reply-To: <46EC2D5A.7080504@intel.com>

Kok, Auke wrote:
> James Chapman wrote:
>> Kok, Auke wrote:

>>>>      rx_long_byte_count: 34124849453
>>
>> Are these long frames expected in your network? What is the MTU of the 
>> transmitting clients? Perhaps this might explain why reads work 
>> (because data is coming from the Linux box so the packets have smaller 
>> MTU) while writes cause delays or packet loss because the clients are 
>> sending long frames which are getting fragmented?
> 
> those are not "long frames" but the number of bytes the hardware counted 
> in its "long" data type based byte counter.

Thanks for correcting me, Auke.

Should this counter be renamed to avoid someone else making this mistake 
in the future? Just a thought.

-- 
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development


  parent reply	other threads:[~2007-09-16 16:24 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14  2:04 e1000 driver and samba L F
2007-09-14 17:18 ` Kok, Auke
2007-09-14 18:40   ` L F
2007-09-14 20:59     ` Kok, Auke
2007-09-15  0:37       ` L F
2007-09-15  5:09         ` Bill Fink
2007-09-15 12:27           ` L F
2007-09-15 12:44             ` L F
2007-09-15 17:44       ` James Chapman
2007-09-15 19:07         ` Kok, Auke
2007-09-16  4:06           ` L F
2007-09-16  5:04             ` Kok, Auke
2007-09-17 16:42               ` L F
2007-09-17 17:02                 ` Kok, Auke
2007-09-17 18:58                   ` L F
2007-09-17 21:01                     ` Brandeburg, Jesse
2007-09-18  6:03                       ` Bill Fink
2007-09-18  7:45                         ` Urs Thuermann
2007-09-18  8:47                           ` Bill Fink
2007-09-18 13:39                           ` Florian Weimer
2007-09-18 16:32                             ` L F
2007-09-18 17:04                               ` Tantilov, Emil S
2007-09-19 14:53                                 ` L F
2007-09-20  2:51                                   ` Bill Fink
2007-09-21 14:08                                     ` L F
2007-09-20  4:53                                   ` Bill Fink
2007-09-18 16:44                             ` Bill Fink
2007-09-17 18:02               ` Rick Jones
2007-09-17 18:51                 ` Kok, Auke
2007-09-16 16:24           ` James Chapman [this message]
2007-09-16 20:03             ` Kok, Auke
2007-09-16  4:07         ` L F
2007-09-14 18:26 ` Francois Romieu
2007-09-14 18:41   ` L F
  -- strict thread matches above, loose matches on Subject: below --
2007-09-20 23:30 Bruce Cole
2007-09-21 14:13 ` L F
2007-09-21 18:21   ` Bruce Cole
2007-09-21 21:49 ` Francois Romieu
2007-09-21 22:01   ` Bruce Cole
2007-09-21 22:41     ` Francois Romieu

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=46ED58AF.1070000@katalix.com \
    --to=jchapman@katalix.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=lfabio.linux@gmail.com \
    --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.