All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: David Miller <davem@davemloft.net>
Cc: Netdev <netdev@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: irq_fpu_usable() is false in ndo_start_xmit() for UDP packets
Date: Mon, 16 Nov 2015 22:28:52 +0100	[thread overview]
Message-ID: <CAHmME9qDJnfJgerxwwG8_dMvse7oim=sDdPzQo=DRi_S0Ym=Ew@mail.gmail.com> (raw)
In-Reply-To: <20151116.161746.1472467067664450149.davem@davemloft.net>

On Mon, Nov 16, 2015 at 10:17 PM, David Miller <davem@davemloft.net> wrote:
>
> Not without a complete redesign of the x86 fpu save/restore mechanism.

Urg, okay. I still wonder why irq_fpu_usable() is true when using TCP but not
when using UDP... Any ideas on this?

> The driver is the wrong place to do software cryptographic transforms
> anyways.
> Judging from your other emails, you doing a lot of weird shit in your
> driver.
> Maybe you should just tell us exactly what kind of device it is for,
> exactly what the features and offloads are, and maybe we can tell you
> therefore what kind of facilities would match that situation best.
> You're currently trying to do it the other way, you know everything
> about your device and goals, and you're sending us small piecemeal
> questions.  We lack the high level full picture of your device, so
> it's hard for us to give you good answers.

Yes, this is fair to ask. Here it goes:

I'm making a simpler replacement for IPSec that operates as an device
driver on the interface level, rather than the IPSec xfrm method. The
methodology is going to be controversial, so I'm taking my time
perfecting each component, and then I'm planning on writing in with a
big email explaining why, with justifications, and numbers. It has
some real world benefits that are already quantifiable. If you're
curious, I did a talk on it at Kernel Recipes in Paris [1]. But
please, give me some time to finish things and prepare myself. I want
to present it to you in the best way possible. I'd hate for it to be
dismissed too early or too hastily, before it's had its chance.

[1] https://www.youtube.com/watch?v=9Rk4doELmwM

  reply	other threads:[~2015-11-16 21:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 19:52 irq_fpu_usable() is false in ndo_start_xmit() for UDP packets Jason A. Donenfeld
2015-11-16 20:32 ` David Miller
2015-11-16 20:58   ` Jason A. Donenfeld
2015-11-16 21:17     ` David Miller
2015-11-16 21:28       ` Jason A. Donenfeld [this message]
2015-11-16 21:33         ` David Miller
2015-11-16 21:37           ` Jason A. Donenfeld
2015-11-16 22:27     ` Hannes Frederic Sowa
2015-11-16 23:57       ` Jason A. Donenfeld
2015-11-17  0:04         ` Jason A. Donenfeld
2015-11-17 12:38   ` David Laight

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='CAHmME9qDJnfJgerxwwG8_dMvse7oim=sDdPzQo=DRi_S0Ym=Ew@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=davem@davemloft.net \
    --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 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.