From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] ML
Date: Wed, 9 Feb 2022 08:52:31 -0800 [thread overview]
Message-ID: <CALQXh-PzK3fYyfMh=nndk6DS3L0S5Xh65A1SaOP9hXUHDV5DWA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5S_fBFssDbApyF-XGCkzaDxv8hvNWe0zVRwcft80CzOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
Only if you tell it to...
For stuff like this, my understanding is that the hard part is always in
the labelling of the training data. I've been ML-adjacent for the last
~decade, but not doing ML myself. I really should sit down and do some
model training on various kinds of datasets that would be of interest to me
(logs from my router, samples of rtt to various places, from points within
my network, etc.)
On Wed, Jan 19, 2022 at 6:34 PM Dave Taht <dave.taht@gmail.com> wrote:
> ... but can it see bloat?
>
>
> https://developer.nvidia.com/blog/accelerating-next-generation-cybersecurity-morpheus-now-with-expanded-early-access/
>
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 1807 bytes --]
prev parent reply other threads:[~2022-02-09 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 2:34 Dave Taht
2022-02-09 16:52 ` Aaron Wood [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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALQXh-PzK3fYyfMh=nndk6DS3L0S5Xh65A1SaOP9hXUHDV5DWA@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--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