netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: dhlii@dlasys.net
Cc: netdev@vger.kernel.org
Subject: Re: Puzzling driver problem
Date: Tue, 12 May 2009 13:32:19 +0100	[thread overview]
Message-ID: <1242131539.3935.17.camel@deadeye> (raw)
In-Reply-To: <4A08F777.6040605@dlasys.net>

On Tue, 2009-05-12 at 00:13 -0400, David H. Lynch Jr. wrote:
> I am working on a driver for the Xilinx Local Link Fifo Temac.
>     It is based on an earlier driver for very similar hardware that uses
> a scatter gather DMA engine rather than a FIFO.
>     95% of the code is common.
>     The FIFO code is also tested independently in a bootloader and works
> fine there.
> 
>     The problem I am having is that after the driver and linux load.
>     HTTP requests to the busy box web server hang after just a few HTTP
> packets.
>    
>     Many other protocols seem to be working just fine. I can send
> thousands of pings and get responses,
>     I can SSH to the embedded linux running the driver.
>     Using a packet sniffer (wireshark) aside from the HTTP stalling,
> nothing looks extrodinary.
>     Other packets are getting through and being replied
[...]

Is it possible that you are setting the maximum frame length
incorrectly?  HTTP is likely to use maximum-length frames for responses
whereas ping, SSH (aside from file transfer) and TFTP will use smaller
frames.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

      reply	other threads:[~2009-05-12 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  4:13 Puzzling driver problem David H. Lynch Jr.
2009-05-12 12:32 ` Ben Hutchings [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=1242131539.3935.17.camel@deadeye \
    --to=bhutchings@solarflare.com \
    --cc=dhlii@dlasys.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).