Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Joshua Cameron <joshua@codedev.com.au>
To: wireguard@lists.zx2c4.com
Subject: Fwd: WireGuard TODO
Date: Sat, 23 Mar 2019 19:44:19 +1100	[thread overview]
Message-ID: <CAPmo8Nxxj_fpLa9yS7onEv8obgYa-EakoFE4sk_yGDJER4hmgA@mail.gmail.com> (raw)
In-Reply-To: <CAPmo8Nxysn5r_24xOuV7OrZYURCXp8i_2g9GzEeL0X1tDvE-1A@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 998 bytes --]

Hey guys,

Not sure where it would be best to post this?

Cheers!

---------- Forwarded message ---------
From: Joshua Cameron <joshua@codedev.com.au>
Date: Sat, Mar 23, 2019 at 12:41 AM
Subject: WireGuard TODO
To: <jason@zx2c4.com>


Hey Jason,

My name is Joshua and I'm a software developer living/working in Sydney
Australia.
I've come across your WireGuard project this week, read the whitepaper,
watched the Linux Plumbers presentation, and read some of the relevant
Linux mailing list archives.

I've become very interested in your project and I'd love to find a way to
contribute my free time. My own programming interests include high
throughput/low latency processing, so I'd like to suggest myself as someone
to look into two of the TODO's from your site, CPU Auto Scaling and packet
locality.

Was there someone already looking at that? I'd love to have a chat about
your thoughts for it.

Thanks for your consideration, hoping to be a part of the project.

Cheers mate,
Joshua Cameron

[-- Attachment #1.2: Type: text/html, Size: 1522 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

           reply	other threads:[~2019-03-23 18:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAPmo8Nxysn5r_24xOuV7OrZYURCXp8i_2g9GzEeL0X1tDvE-1A@mail.gmail.com>]

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=CAPmo8Nxxj_fpLa9yS7onEv8obgYa-EakoFE4sk_yGDJER4hmgA@mail.gmail.com \
    --to=joshua@codedev.com.au \
    --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).