Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 17 Jan 2018 22:58:36 +0100 (CET)
From:   Thomas Gleixner <tglx@linutronix.de>
To:     Linus Torvalds <torvalds@linux-foundation.org>
cc:     David Miller <davem@davemloft.net>, Mike Galbraith <efault@gmx.de>,
        Peter Zijlstra <peterz@infradead.org>,
        Eric Dumazet <edumazet@google.com>,
        Dmitry Safonov <dima@arista.com>,
        Frederic Weisbecker <frederic@kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Dmitry Safonov <0x7f454c46@gmail.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Frederic Weisbecker <fweisbec@gmail.com>,
        Hannes Frederic Sowa <hannes@stressinduktion.org>,
        Ingo Molnar <mingo@kernel.org>,
        Sasha Levin <alexander.levin@verizon.com>,
        Paolo Abeni <pabeni@redhat.com>,
        Paul McKenney <paulmck@linux.vnet.ibm.com>,
        Radu Rendec <rrendec@arista.com>,
        Rik van Riel <riel@redhat.com>,
        Stanislaw Gruszka <sgruszka@redhat.com>,
        Wanpeng Li <wanpeng.li@hotmail.com>
Subject: Re: [RFC 1/2] softirq: Defer net rx/tx processing to ksoftirqd
 context
In-Reply-To: <CA+55aFwmvoz0MQGdwC+bNh40SEDTXt2F_rJuPr3CxpX_O+jo=w@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1801172258080.2326@nanos>
References: <1515782670.7007.3.camel@gmx.de> <20180117.153049.1803664333084879932.davem@davemloft.net> <CA+55aFwOv1SBOz6+0GxLxbK5riei83AQRJEHUTXUehSWfBq=Fg@mail.gmail.com> <20180117.164932.1269304606476934540.davem@davemloft.net>
 <CA+55aFwmvoz0MQGdwC+bNh40SEDTXt2F_rJuPr3CxpX_O+jo=w@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, 17 Jan 2018, Linus Torvalds wrote:

> On Wed, Jan 17, 2018 at 1:49 PM, David Miller <davem@davemloft.net> wrote:
> >
> >> That said, this made me wonder a bit. I wonder how bounded the latency
> >> is for raising a softirq from process context. We only _check_ the
> >> softirq on the last hardirq exit, I think.
> >
> > System call return checks it, otherwise this situation would be
> > completely bolixed.
> 
> That's what I thought too. But then I went and looked, and I can't find it.
> 
> But you're probably right, and I just missed it.

Not really. There is nothing to see there.

Thanks,

	tglx