From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Dave Taht <dave.taht@gmail.com>, Jonathan Morton <chromatix99@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cake] Van Jacobson at netdevconf earlier this week
Date: Mon, 16 Jul 2018 08:04:16 -0400 [thread overview]
Message-ID: <c284f077-df00-1375-5d6b-c2a833bcec3a@mojatatu.com> (raw)
In-Reply-To: <CAA93jw6d08vJj-q0cwm9MOUT9NOWH0AGPK5fyXeq6MyPkfPV3Q@mail.gmail.com>
We are an engineering conference(lanman appears to be academic)
tied to Linux networking only. To get a sense, last schedule:
https://www.netdevconf.org/0x12/schedule.html
For selfish reason I hope we stay small because it is a lot more
intimate (but i worry because the attendance is growing).
Mainstream media doesnt fit well with our crowd. We talked to lwn
but unfortunately they couldnt send anyone. They will, however,
interview Van. An attendee wrote up something on Van's keynote:
https://jvns.ca/blog/2018/07/12/netdev-day-2--moving-away-from--as-fast-as-possible/
Van's keynote I believe is _very influential_. NIC vendors were
present and I am sure you'll start seeing NICs supporting his ideas
in the very near future.
We are working on cleaning/cutting/editing videos - they should
be up soon. Likely the slides will go up first; then papers before
you see videos.
Next conference is in Prague Mar 20-22 2019. We do not accept
recycled talks - so if you are going on a "tour" start with us.
You can look at an option for submitting a tutorial perhaps.
cheers,
jamal
On 15/07/18 11:35 AM, Dave Taht wrote:
> On Fri, Jul 13, 2018 at 6:57 PM Jonathan Morton <chromatix99@gmail.com> wrote:
>>
>>> On 14 Jul, 2018, at 1:22 am, Dave Taht <dave.taht@gmail.com> wrote:
>>>
>>> I look forward to the press coverage and videos of these sessions.
>>
>> Did you get anything like that from LANMAN?
>
> Lanman is a very small conference. I viewed my preso there as an alpha
> test for future conferences. At one level
> going on the road again at this point, to talk to the wisp, 5g, rdk,
> netdevconf, and ietf folk makes sense, at another, well... lacking
> travel budget, graphic sense, and patience, makes it intimidating.
> Still, I am trying to summon up the gumption to go on the road
> again... or at least do talks in my local area.
>
> netdevconf is also a very small conference. Although I think highly of
> what they are doing (being far more technical and linux grassroots
> oriented, than LF, and going back to back with ietf in the hope that
> some folk and ideas bleed across), I was being sarcastic about even VJ
> getting any coverage from the press. I doubt anyone we know in the
> tech press was there, not ars, not wired - not even sure if lwn sent
> anyone.
>
> do hope various talks were filmed though.
>
>> - Jonathan Morton
>>
>
>
next prev parent reply other threads:[~2018-07-16 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 22:22 [Bloat] " Dave Taht
2018-07-14 1:57 ` [Bloat] [Cake] " Jonathan Morton
2018-07-15 15:35 ` Dave Taht
2018-07-16 12:04 ` Jamal Hadi Salim [this message]
2018-07-16 15:09 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c284f077-df00-1375-5d6b-c2a833bcec3a@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.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