From: Steffen Klassert <steffen.klassert@secunet.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: <netdev@vger.kernel.org>, Sowmini Varadhan <sowmini.varadhan@oracle.com>
Subject: Re: IPsec workshop/BoF at netdev1.1?
Date: Tue, 8 Dec 2015 12:30:02 +0100 [thread overview]
Message-ID: <20151208113002.GJ14008@secunet.com> (raw)
In-Reply-To: <1449505201.25029.61.camel@edumazet-glaptop2.roam.corp.google.com>
On Mon, Dec 07, 2015 at 08:20:01AM -0800, Eric Dumazet wrote:
> On Mon, 2015-12-07 at 13:00 +0100, Steffen Klassert wrote:
> > Is there any interest in doing an IPsec workshop/BoF at netdev1.1?
> >
> > This mail is to probe if we can gather enough discussion topics to run
> > such a workshop/BoF. So if someone is interested to attend and/or has a
> > related discussion topic, please let me know.
> >
> > My current topics:
> >
> > - Adding a software GRO/GSO codepath for IPsec. I have working example code,
> > a RFC version could be ready before the netdev conference.
>
>
> - Remove rwlock usage (xfrm_policy_lock) from fast path and szitch to
> RCU ?
Good point. I add it to the topic list, thanks!
prev parent reply other threads:[~2015-12-08 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 12:00 IPsec workshop/BoF at netdev1.1? Steffen Klassert
2015-12-07 12:19 ` Sowmini Varadhan
2015-12-07 16:20 ` Eric Dumazet
2015-12-08 11:30 ` Steffen Klassert [this message]
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=20151208113002.GJ14008@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.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 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.