From: "David S. Miller" <davem@davemloft.net>
To: chris.leech@gmail.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC][PATCH 4/5] I/OAT DMA support and TCP acceleration
Date: Tue, 20 Dec 2005 23:37:39 -0800 (PST) [thread overview]
Message-ID: <20051220.233739.30595170.davem@davemloft.net> (raw)
In-Reply-To: <41b516cb0512202310q78d5a25apab3c9d6fbb17089e@mail.gmail.com>
From: Chris Leech <chris.leech@gmail.com>
Date: Tue, 20 Dec 2005 23:10:07 -0800
> That could be a good way to deal with it. Actually, I should double
> check the length of tcp_skb_cb. I took a quick look and thought that
> there might be some room left there anyway, even though the comment in
> tcp.h says otherwise.
There isn't, it's basically full on 64-bit systems with ipv6 enabled.
Just put the DMA cookie object explicitly into struct sk_buff,
protected by CONFIG_NET_DMA.
next prev parent reply other threads:[~2005-12-21 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 5:17 [RFC][PATCH 4/5] I/OAT DMA support and TCP acceleration Chris Leech
2005-12-21 6:20 ` Eric Dumazet
[not found] ` <41b516cb0512202305p45439464o6b7ba6c2c88062bc@mail.gmail.com>
2005-12-21 7:10 ` Fwd: " Chris Leech
2005-12-21 7:37 ` David S. Miller [this message]
2005-12-21 7:35 ` David S. Miller
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=20051220.233739.30595170.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chris.leech@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).