diff for duplicates of <1216882823.7257.229.camel@twins> diff --git a/a/1.txt b/N1/1.txt index e91bff2..63f65c4 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ On Wed, 2008-07-23 at 13:14 -0700, David Miller wrote: -> From: Peter Zijlstra <peterz@infradead.org> +> From: Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> > Date: Wed, 23 Jul 2008 12:58:16 +0200 > > > So I guess my question is, is netif_tx_lock() here to stay, or is the @@ -34,3 +34,8 @@ down-side of stretching this limit is that deep lock chains come with costs (esp so on -rt), so I'm not particularly eager to grow this - it might give the impresssion its a good idea to have very long lock chains. + +-- +To unsubscribe from this list: send the line "unsubscribe linux-wireless" in +the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 526dd75..4a3bc46 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,23 +2,24 @@ "ref\020080723101352.GD4561@ff.dom.local\0" "ref\01216810696.7257.175.camel@twins\0" "ref\020080723.131441.200166513.davem@davemloft.net\0" - "From\0Peter Zijlstra <peterz@infradead.org>\0" + "ref\020080723.131441.200166513.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org\0" + "From\0Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>\0" "Subject\0Re: Kernel WARNING: at net/core/dev.c:1330 __netif_schedule+0x2c/0x98()\0" "Date\0Thu, 24 Jul 2008 09:00:23 +0200\0" - "To\0David Miller <davem@davemloft.net>\0" - "Cc\0jarkao2@gmail.com" - Larry.Finger@lwfinger.net - kaber@trash.net - torvalds@linux-foundation.org - akpm@linux-foundation.org - netdev@vger.kernel.org - linux-kernel@vger.kernel.org - linux-wireless@vger.kernel.org - " mingo@redhat.com\0" + "To\0David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>\0" + "Cc\0jarkao2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" + Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org + kaber-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org + torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org + akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org + netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + " mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org\0" "\00:1\0" "b\0" "On Wed, 2008-07-23 at 13:14 -0700, David Miller wrote:\n" - "> From: Peter Zijlstra <peterz@infradead.org>\n" + "> From: Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>\n" "> Date: Wed, 23 Jul 2008 12:58:16 +0200\n" "> \n" "> > So I guess my question is, is netif_tx_lock() here to stay, or is the\n" @@ -52,6 +53,11 @@ "down-side of stretching this limit is that deep lock chains come with\n" "costs (esp so on -rt), so I'm not particularly eager to grow this - it\n" "might give the impresssion its a good idea to have very long lock\n" - chains. + "chains.\n" + "\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-wireless\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -a81f3c23ebe2d10441a68d7676194b5603907a1ac55ab91b06d61c439fe4f944 +f69c2f5da4fda5c7a350f6323b26d1dfbbbd7d70d0a495a0d6c195a1b79bb581
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.