linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-mips@linux-mips.org, linux-mm@kvack.org,
	WireGuard mailing list <wireguard@lists.zx2c4.com>,
	k@vodka.home.kg
Subject: Re: Proposal: HAVE_SEPARATE_IRQ_STACK?
Date: Thu, 10 Nov 2016 18:39:54 +0100	[thread overview]
Message-ID: <CAHmME9rv8CfgY87S_HVN3njc2RnisjoxzfZxY=H=2FzZkrQqLg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611101351260.3501@nanos>

Hi Thomas,

On Thu, Nov 10, 2016 at 2:00 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> Do not even think about going there. That's going to be a major
> mess.

Lol! Okay. Thank you for reigning in my clearly reckless
propensities... Sometimes playing in traffic is awfully tempting.

>
> As a short time workaround you can increase THREAD_SIZE_ORDER for now and
> then fix it proper with switching to seperate irq stacks.

Okay. I think in the end I'll kmalloc, accept the 16% slowdown [1],
and focus efforts on having a separate IRQ stack. Matt emailed in this
thread saying he was already looking into it, so I think by the time
that slowdown makes a difference, we'll have the right pieces in place
anyway.

Thanks for the guidance here.

Regards,
Jason

[1] https://git.zx2c4.com/WireGuard/commit/?id=cc3d7df096a88cdf96d016bdcb2f78fa03abb6f3

  reply	other threads:[~2016-11-10 17:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09 21:27 Proposal: HAVE_SEPARATE_IRQ_STACK? Jason A. Donenfeld
2016-11-09 21:40 ` Thomas Gleixner
2016-11-09 23:34   ` Jason A. Donenfeld
2016-11-10  9:03     ` Thomas Gleixner
2016-11-10 11:41       ` Jason A. Donenfeld
2016-11-10 13:00         ` Thomas Gleixner
2016-11-10 17:39           ` Jason A. Donenfeld [this message]
2016-11-10 16:36         ` Matt Redfearn
2016-11-10 17:37           ` Jason A. Donenfeld
2016-11-10  0:17 ` David Daney
2016-11-10  1:47   ` Jason A. Donenfeld

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='CAHmME9rv8CfgY87S_HVN3njc2RnisjoxzfZxY=H=2FzZkrQqLg@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=k@vodka.home.kg \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mm@kvack.org \
    --cc=tglx@linutronix.de \
    --cc=wireguard@lists.zx2c4.com \
    /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).