►
From YouTube: 2019-10-29 :: Crimson SeaStor OSD Weekly Meeting
Description
.
A
A
B
B
C
C
All
the
open,
channel,
SSD
and
I
also
find
that
there
are
some
ten
simulators
which
we
could
be,
which
you
could
we
could
leverage
it
to
on
telling
the
behavior
of
of
the
flash
with
SF
Kia
or
without
it
it
could
be
helped
away
when
we
are
prototyping,
the
OPA
store.
E
There's
good
news
on
that
front:
I
heard
from
Matt
yesterday
we
ought
to
be
able
to
get
some
prototype
zone
Ned
as
the
NS
SSDs,
like
real
soon
that
he
asked
for
an
address
to
ship
them
to
so
I.
Think
we're
or
even
we
should
happen
weeks,
I
hope,
although
somehow
these
things
always
take
longer
than
they're
supposed
to,
but
still.
F
E
E
E
E
One
thing
I
want
to
suggest
is:
try
to
separate
out
like,
for
instance,
do
it
one
file
at
a
time,
birds
it's
for
South
context,
but
make
that
its
own
commit,
because
it's
good
just
give
me
a
whole
bunch
of
like
mechanical
changes
to
a
bunch
of
files.
If
you
make
out
its
own,
commit
it'll,
be
really
really
quick
to
review.
B
B
B
E
The
reason
for
the
pre
declaration
in
most
of
those
cases
is
not
pop
is
not
too
polluted
that
that
header
with
the
Ceph
context
declaration.
In
those
cases
it's
only
passed
by
pointer,
so
it
doesn't
need
the
full
implementation,
just
the
just
the
declaration.
So
my
suggestion
is
that
you,
you
keep
it
pretty
mechanical
for
files
that
are
only
part
of
clásicos.
These
simply
switch
it
to
namespace
def
common
around
the
class
declaration
for
files
that
are
used
by
both
use
the
top
namespace.
B
E
Does
that
make
sense
that
way?
It'll
be
you
know,
it'll
always
be
correct.
If
it's,
if
it's
included
into
the,
if
it's
included
in
all
three
places,
it'll
get
the
right
namespace
in
all
three
places.
If
it's
only
in
classic,
then
don't
worry
about
it
doesn't
matter.
You
just
need
to
include
this
F
common
part
or,
if
you
prefer,
you
could
just
make
it
always
use
top
to
top
namespace.
It
doesn't
matter
to
me.
E
B
E
B
E
One
of
these
things
that's
used
in
more
than
one
place.
We
actually
want
to
change
the
way
they're
used
in
classic
OST,
because
otherwise
this
will
be
terribly
confusing.
We'll
have
symbols
that
exist
both
in
the
top,
unqualified
namespace
and
in
deeper
namespaces
and
they'll
all
be
visible,
which
I
think
we
very
much
don't
want,
and
it's
worth
doing
some
work
to
of
avoid
all
so
honestly,
this
improves
the
code.
We've
done
this
in
a
few
places
already,
just
as
a
side
effect
of
modifying
the
code.
It
usually
improves
readability.
E
B
E
C
B
C
E
B
B
C
D
A
D
With
last
week,
I
sent
a
bunch
of
peers
to
the
step,
/
sister
Reaper.
Basically,
it's
work
somehow
related
to
a
writer
that
the
main
the
main
thing
the
evidence
of
temporary
spawning
cannot
pass
has
been
reworked
to
actually
don't
change
the
observable
behavior
of
Afghan
and
and
enwrapped.
Actually,
this
comic
is
longer
than
the
term
the
the
important
part.
Still
it's
and
it's
it's
research,
the
benefit
we
saw
during
a
writer
testing.
D
A
D
D
Well
idea:
I
used
to
have
to
have
a
something
something
like
a
gift
for
Abby.
We
will
need
to.
We
need
to
make
some
discs
some
profile,
that's
related
to
the
buffer,
fit
in
efficient
consumption
of
DPD,
KY
and
I
mean
input
buffer
factory
and
also
a
spiracle
integrations.
A
lot
of
potential
modifications
to
sister.
D
A
A
A
A
A
A
List
it
I
think
I
said
that
last
week,
I
enlisted
a
the
new
intern.
We
have
to
help
me
testing.
The
problem
is,
is
that
he
disappears.
He
comes
only
once
or
twice
a
week
and
this
week
II
wasn't
feeling
well,
so
nothing
much
was
done
by
him,
yet
so
more
or
less.
This
is
what
what
I'm
doing
and
I'm
nearing
to
have
the
parts
of
the
shock
console.
A
C
A
A
C
F
D
Maybe
not
a
question
just
a
quick
note
on
the
DPD
k,
testing
I
think
it's
it's
extremely
important,
not
even
because
of
the
raw
performance
gain
we
could
get
because
of
switching
to
native
stock.
It's
about
verifying
our
the
the
very
initial
hypothesis
we
made
about
terms
of
problems
in
cross
flow.
As
this
context,
mult
switches
discuss
actually
yeah
because
of
because
of
using
the
POSIX
tag,
we
have
the
very
last.
D
This
called
interactions
in
entire
Chrome
OS
d.
It's
actually
it's
quite
an
right
now,
more
or
less
familiar,
just
let's
say:
ASIC
messenger
classical
as
ASIC
messenger,
combined
with
object
stir
and
what
is
funny
it's
that
we
are.
We
are
when
you
are
our
profiling,
classical
just
messenger
threat
of
classical
OSD.
You
are
you
very
similar
of
that
similar
IPC
instruction
per
cycle
ratio
in
comparison
to
what
we
have
at
the
common
criminal
I'm
I
am
Creek
Emily
I'm
extremely
curious.
D
How
the
IPC
would
like,
after
getting
rid
of
those
very
last
Cisco's
we
have
because
of
the
network
interaction.
It
will
be
extremely
important
topic
for
also
for
for
the
Feast
of
discussion.
I
mean
SPD
K
integration,
to
judge
how
important
it
really
is
where,
when
a
stage
we
should,
we
should
preceding
it
whether
we
want
to
focus
on
SPD
K,
even
at
the
beginning
phase,
or
maybe
postpone
it
a
bit
I.
F
D
D
C
C
F
F
A
C
E
A
short
update,
I've
got
the
other
context
reference
or
at
the
outer
context,
patch
up
for
PR
waiting
for
their
crimson
perf
thing
to
go
through,
but
it
sounds
like
we
know
what's
wrong
with
her
generally
still
making
slow
progress
in
the
crimson
back
for
recovery
stuff.
That's
a
do.
E
Yep,
like
I,
said
we
are
going
to
get
DNS
drives
the
next
few
weeks.
That'll
be
good
after
context.
Er
should
be
pretty
close
to
radio
at
least
once
crimson,
perfect
routes
that
I
didn't
break
through
put
bands
to
working
on
back
full
recovery.
It's
not
going
quickly,
but
I
am
making
progress.
That's
it.