From: Chris Leech <chris.leech@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>, netdev <netdev@vger.kernel.org>
Subject: Fwd: [RFC][PATCH 4/5] I/OAT DMA support and TCP acceleration
Date: Tue, 20 Dec 2005 23:10:07 -0800 [thread overview]
Message-ID: <41b516cb0512202310q78d5a25apab3c9d6fbb17089e@mail.gmail.com> (raw)
In-Reply-To: <41b516cb0512202305p45439464o6b7ba6c2c88062bc@mail.gmail.com>
Sorry, bounced from vger the first time due to formatting
---------- Forwarded message ----------
From: Chris Leech <christopher.leech@intel.com>
Date: Dec 20, 2005 11:05 PM
Subject: Re: [RFC][PATCH 4/5] I/OAT DMA support and TCP acceleration
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: lkml <linux-kernel@vger.kernel.org>, netdev
<netdev@vger.kernel.org>, "Grover, Andrew" <andrew.grover@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>
On 12/20/05, Eric Dumazet <dada1@cosmosbay.com> wrote:
> Please consider not enlarging cb[] if not CONFIG_NET_DMA ?
>
> I mean, most machines wont have a compatable NIC, so why should they pay the
> price (memory, cpu) in a critical structure named sk_buff ?
>
> #ifdef CONFIG_NET_DMA
> typedef dma_cookie_t net_dma_cookie_t;
> #else
> typedef struct {} net_dma_cookie_t;
> #endif
>
> ...
>
> char cb[40+sizeof(net_dma_cookie_t)];
>
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.
-Chris
next prev parent reply other threads:[~2005-12-21 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 5:17 Chris Leech
2005-12-21 6:20 ` Eric Dumazet
[not found] ` <41b516cb0512202305p45439464o6b7ba6c2c88062bc@mail.gmail.com>
2005-12-21 7:10 ` Chris Leech [this message]
2005-12-21 7:37 ` David S. Miller
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=41b516cb0512202310q78d5a25apab3c9d6fbb17089e@mail.gmail.com \
--to=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
all inboxes | Powered by JetHome®