netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bunk@kernel.org
Cc: shemminger@linux-foundation.org, netdev@vger.kernel.org,
	christopher.leech@intel.com, shannon.nelson@intel.com,
	dan.j.williams@intel.com
Subject: Re: [2.6 patch] unexport softnet_data
Date: Fri, 26 Oct 2007 04:19:06 -0700 (PDT)	[thread overview]
Message-ID: <20071026.041906.223457165.davem@davemloft.net> (raw)
In-Reply-To: <20071024162425.GI30533@stusta.de>

From: Adrian Bunk <bunk@kernel.org>
Date: Wed, 24 Oct 2007 18:24:25 +0200

> The EXPORT_PER_CPU_SYMBOL(softnet_data) is no longer used.
> 
> Signed-off-by: Adrian Bunk <bunk@kernel.org>

I wanted to apply this, but in validing the patch I noticed
what appears to be an omission in TCP ipv6.

It seems that NET_DMA support there is only half-cooked and
the following patch is needed (and thus there is a modular
use of softnet_data again).

Looking at Christopher Leech's original TCP I/O AT commit:

1a2449a87bb7606113b1aa1a9d3c3e78ef189a1c

this appears to just be an oversight.

If one of the current I/O AT folks can look this over and
confirm I'd appreciate it.

Thanks!

[TCP]: Add missing I/O AT code to ipv6 side.

Signed-off-by: David S. Miller <davem@davemloft.net>

diff --git a/net/ipv6/tcp_ipv6.c b/net/ipv6/tcp_ipv6.c
index 32dc329..06fa4ba 100644
--- a/net/ipv6/tcp_ipv6.c
+++ b/net/ipv6/tcp_ipv6.c
@@ -1732,6 +1732,8 @@ process:
 	if (!sock_owned_by_user(sk)) {
 #ifdef CONFIG_NET_DMA
 		struct tcp_sock *tp = tcp_sk(sk);
+		if (!tp->ucopy.dma_chan && tp->ucopy.pinned_list)
+			tp->ucopy.dma_chan = get_softnet_dma();
 		if (tp->ucopy.dma_chan)
 			ret = tcp_v6_do_rcv(sk, skb);
 		else

  reply	other threads:[~2007-10-26 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 16:24 [2.6 patch] unexport softnet_data Adrian Bunk
2007-10-26 11:19 ` David Miller [this message]
2007-10-26 15:38   ` Nelson, Shannon
2007-11-07  7:41     ` David Miller
2007-11-07 15:01       ` Nelson, Shannon

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=20071026.041906.223457165.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bunk@kernel.org \
    --cc=christopher.leech@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=shannon.nelson@intel.com \
    --cc=shemminger@linux-foundation.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).