From: Willy Tarreau <willy@w.ods.org>
To: Kallol Biswas <kallol.biswas@s2io.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Fwd: receive path with fragmented skbs
Date: Sat, 31 Jan 2004 08:36:03 +0100 [thread overview]
Message-ID: <20040131073603.GA17225@alpha.home.local> (raw)
In-Reply-To: <1075504343.21310.23.camel@localhost.localdomain>
Hi,
you should have posted this to the netdev list : netdev@oss.sgi.com.
You don't need to resend, I have CC'd it.
Willy
On Fri, Jan 30, 2004 at 03:12:24PM -0800, Kallol Biswas wrote:
> Hello,
> We have been developing drivers and networking software on
> a 10 gigabit ethernet adapter from S2io Inc (www.s2io.com). There is a
> requirement that the ethernet header, IP+TCP headers have to be cache
> aligned and the payload and the IP+TCP headers have to be in different
> fragments. So we have created receive path skbs with data size big
> enough to hold the ethernet header and two fragments, one fragment for
> the IP+TCP header and the other for payload. The card can directly dma
> into the three receive scatter buffers when a frame arrives.
>
> We could not get ping working with this design of receive skbs,
> but if a skb is linearized with skb_linearize() before calling
> netif_rx(), ping works.
>
> /proc/net/snmp was printed, no frame had any error. Probably no one has
> ever tested the receive path of the stack with fragmented skbs, am I
> right? One of the ways this problem can be debugged is to find out where
> exactly the packets get dropped. Any comment?
>
> Kallol
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
parent reply other threads:[~2004-01-31 7:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1075504343.21310.23.camel@localhost.localdomain>]
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=20040131073603.GA17225@alpha.home.local \
--to=willy@w.ods.org \
--cc=kallol.biswas@s2io.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).