►
From YouTube: Crimson/Seastar OSD Meeting 2019-01-08
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
B
A
C
A
Okay,
let's
start
from
on
me
last
week,
I
I
was
working
on
putting
up
the
crimson
the
worst
d
and
then
that
there's
some
but
more
importantly,
we
have
a
discussion
regarding
to
the
proposal.
Pi
redox,
singular
idol,
singer,
Stratos,
mister,
deep,
probably
that's
what
what
we
will
be
discussing
the
English
in
the
fall
falling
part
of
history.
They
stand
up
and
in
when
now
I'm
working
when
I'm
working
on
putting
up
community
I
found
that.
A
For
example,
and
when
the
O's
deep
put
up
it
will
check
if
it
is
the
it
is,
it
is
a
up
x
ultimate
and
if
its
address
matches
ways
to
the
ones
noted
in
Austin
map,
it
is
does
not,
it
will
try
to
recruit
itself,
but
before
the
veto
transition.
The
addresses
event
that
an
eternity
is
a
single
which
means
that
it
only
single
addressing
in
in
the
represents
by
a
entity
but
others
beautiful
transition
against
earth.
A
A
A
A
Think
is
that's
what
what
I
found
is
the
tip
of
iceberg.
It's
the
thing
I
found
is
that
in
invade
to
each
energy
can
can
be
bounded
to
multiple
addresses
so
finger
during
the
in
the
take
peyote.
For
example,
if
you
get
a
dress
in
English
in
v1,
if
you
get
to
a
spy
fighters
fight
rights
ID,
only
a
single
address
will
be
with
replied,
return
and
have
to
be
to
transition.
A
A
A
I'm,
not
a
question,
but
we
can
probably
I
can
send
you
to
the
mail
regarding
to
the
background
of
the
v-2
transition
and
why
we
want
to
include
this
feature.
Ok,
I!
Don't
think
it's
quite
it's
a
little
bit
off
topic
and
regarding
to
this,
the
problem
west
were
facing,
but
the
important
important
though.
B
B
Then
I'm
bike,
Wednesday
I'm
working
on
some
there's
some
comments
from
riddles
to
make
a
little
change
and
the
memory
star
test
case
and
then
read
out
such
suggested.
We
add
encapsulation
for
the
objects,
talk
so
I'm,
considering
that
and
you're
working
on
gauge,
so
I
I'm
going
to
show
what
it
looks
like
here.
So.
B
B
Future
lies
the
object
stuff.
The
that
object
star
will
define
some
define
some
words.
You
were
true
API,
the
similar
as
the
object
stop,
but
yet
the
return
is
C
star
future.
So
the
input
is
the
same.
I
keep
the
same
asked
about
your
co-star,
the
input.
The
parameters
are
the
same
and
the
earth
project
tab
is
the
same
and
the
punt
return
the
sea
star
future.
So
for
the
every
object
out,
you
find
the
API
I
will
implemented
encapsulation
all
with
the
same
input
and
output.
Part
of
the
return
as
the
sea
star
future.
B
This
one
is
not
adapter,
it's
just
a
different
in
the
same
interface
as
the
object
star,
but
it'll
return.
Its
is
the
these
are
future
and
the
back
adapter
looks
like
this:
one
I
get
the
caucus,
adapter
a
cottage
align,
align,
object,
object,
object,
star
and,
and
it
will
implement
a
today,
the
the
sister
future
in
your
face-
and
this
looks
like
this
one,
for
example-
always
not
be
there
to
see
something
like
that
in
this
function
of
the
pod
Oh
in
this
Allah
object.
Stop
the
defender,
defender,
thread,
pool
and
object,
stop.
B
In
the
my
object
star,
we
will
define
the
DA
and
it
will
be
initialized,
oh,
when
called
the
construction
function
constructor
and
for
the
raid
for
the
object
style,
API
Auriga
we
exempt
limited
by
the
spread
of
who
use
this
for
this
pointer
to
gather
this
ready
pool
and
they
use
the
submitted
to
submit
the
true
the
POSIX
right
to
executive.
So
it's
just
a
wrapper.
Only
used
the
pro
to
exactly
the
stalls
read
function.
B
So
first
defined
define
the
worth
your
life
as
the
object
star
in
this.
What
rely
up
not
work
at
the
future
filter
is
the
object
stuff
in
this
class
only
define
the
virtual
function.
The
same
for
the
API
has
the
same
input
parameter
and
output
parameter,
but
it
returns
have
a
sister
future
and
then
in
the
ally,
object
star.
He
Harry
shaded.
The
future
last
object
stopped
and
implemented.
The
need,
api's
and
align
objects.
B
B
B
Realized
objects.
Stop,
so
this
objects
are
just
defined.
The
same
virtual
API
asked
object.
Star
object,
start
you
find
the
money
what
you
API
so
here.
Just
that
you
find
the
same.
I
gave
you
the
example.
The
raid
and
there's
some
few
transaction
not
all
currently
so
create
a
new
collection.
Something
like
that,
and
this
API
has
the
same
input,
parameters
and
output
parameters.
A
B
B
D
D
B
D
I'm
not
sure
that
I
will
I
see
I
think
we
will
get
in
the
first
phase
at
least
two
implementations
of
it.
One
will
be
the
adapter
for
currently
existing
object
stars,
but
the
second
I
guess
even
more
important
one
would
be
just
fertilized
münster
implementation,
just
for
testing
and
just
for
very
quick
development.
D
Course,
of
course,
but
it
has
some
drawbacks
first
of
all
is
that
you
need
to
go
through
the
Krauss.
You
need
to
cross
the
carb
boundary.
It
means
it
will
affect
the
performance
ii
think
I
am
afraid
it's
just
not,
and
it
won't
be
enough
to
just
wrap
the
calls
from
currently
existing
objects.
Third
I
am
afraid
we
would
also
need
to
take
about
ensuring
about
take
you
about
making
safety
for
the
parameters
of
the
calls
to
cross
our
boundary
I
mean
especially
the
buffer
list
parameters.
D
D
So
maybe
we
don't
need
to
worry
about
about
serving
any
object,
store
implementation.
We
have
right
now,
of
course,
in
the
later
perspective,
I
guess
I
think
it
will
be,
it
will
be
needed,
but
just
for
from
the
testing
perspective,
a
monster
instance
could
be
enough
and
from
the
testing
perspective
it
will
be
even
better
to
have
the
münster
instance
living
in
the
sister
world,
I
mean
bleeding
on
the
same
on
the
same
reactor
on
the
same
sister
engine,
all
together
with
the
rest
of
the
OSD
and
I
guess
we
can
easily
accomplish
that.
D
B
D
D
B
D
D
D
I
also
think
that
we
might
end
with
just
tingled
engine
repair
criminalize
the
process.
If
so,
it
will
be
the
same.
The
same
would
apply
to
fertilized
münster
instance
and
fertilized
münster
basically
means
that
it
it
will
be
separated
and
from
the
münster
we
have
right
now.
That's
the
reason
why
I
propose
to
in
here,
to
privately
inherit
from
currently
existing
master
and
just
to
expose
really
necessary
things
using
the
using
C++
directive
plus
implement
all
the
new
methods
we
have.
We
have,
in
the
fewest
object,
store
interface.
D
Of
course,
I'm
aware
that
master
has
some
locks
internally,
it
has
even
more
complex
things
and
type
of
readwrite
lock,
but
I
also
would
love
to
point
out
that
most
likely
will
be
able
to
kill
it.
Just
move
I
personally
perceive
the
sister
as
very
damp
very
primitive
CAD
Euler,
with
voluntary
preemption
like
in
the
a
it
is
very
nice
Fink.
By
the
way.
D
This
means
that,
if
you're,
if
you
don't
have,
if
you
don't
declare
any
preemption
point,
you
won't
be
preempted
and
I
think
that
the
preemption
points
in
sister
are
mostly
because
I,
oh,
if
you
are,
if
your
cut
is
if
your
code
is
not
doing
any
I,
oh
no,
no
doesn't
use
the
continuations
concept.
Basically,
it's
free
of
preemption.
D
It
means
that
all
together
with
with
the
idea
of
having
just
one
fret
visiting
using
the
operating
on
the
same
data,
it
means
you
can
have
some
kind
of
wrapper
for
the
read/write
lock,
maybe
well,
maybe
there
it's
right
lock
anyway.
I
think
the
idea
is
to
have
if
def
basically
nullifying
it
for
the
Crimson
wields.
E
A
A
Yeah
one
call
one
reactor
and
one
a
single
object
store
exactly
in
this
context,
is
the
memory
store
so
there's
that,
ideally
there's
a
no,
no,
no
racing
or
no
competition
between
between
different
bit
different
reactor
for
pro
crap
grabbing
the
object
store,
so
there's
no
there's,
no,
no!
No!
No!
The
waiting
for
for
both
for
the
core
for
the
true.
D
It
can
be
that
we
could
consume
münster
even
without
killing,
without
notifying
the
locks
inside
without
notifying
Atomics.
It
currently
has
well
it's
Atomics,
we'll
just
we
would
still
be
memory
barriers,
but
maybe
we
can
live
with
them.
If
not,
we
can
go
even
further
and
kill
them
with
safe
atomic
wrapper,
or
something
like
that.
I'd,
like
that,
the
same
and
with
the
same
idea
with
rich
right
locks,
the
site
is
the
same
idea
with
new
Texas
tonight.
A
I
think
I
think
why
why
would
have
wanted
to
to
emphasize
that
and
memory
store
is
the
it
simpler
for
for
our
current
current
problem.
Currently
we
wanted
to
have
a
we
want
to
test
test
test
and
the
two
per
type
the
the
chromosomal
tea,
to
find.
How
is
it
performance
and
have
a
minimal
minimal
implementations
and
the
the
fast
pass
and
the
the
discussion?
We
have
to
have
a
wrapper
enough
to
have
to
have
a
wrapper
around
existing
for
a
double
boost,
or
that's
the
that's
the
final
goal.
A
We
are
when
we're
trying
to
approach
at
a
stage
of
scrimmage
OSD,
because
we
put
a
lot
of
efforts
on
them
well
and
we
are
putting
a
lot
of
effort
on
the
optimization
of
optimization
and
the
performance
of
the
overall
store.
But
but
I
did
ask
our
state
sterile
stage.
We
are
trying
to
get
a
prototype
prototype
of
a
crystal.
B
A
I
because
you
think
you're
using
design
when
you
we
have
a
ping
pong
between
between
the
two
to
world
and
the
truth.
Probably
two
core
you
know
in
for
the
alien
words
are
backed
by
a
deeper
a
different
course.
The
aliens
read
are
living
on
different
cause,
the
memory,
the
memory
chunk
and
the
task
has
posed
to
different
core
cause,
and
it's
task
queue
so
easily
incur
some
performant
aggression,
which
is
a
is
not
inspected.
I
did
Karen
sterile
because
we
wanted
to
to
see
what
the
what
the
best
performance
we
can
we
can
have.
A
A
D
D
B
A
We
need
to
aware
gets
to
which
part
we
probably
it's
not
performed
performance,
but
that
we
need
to
wear
beware
about
where
it
where
the
performer
could
be
hurt.
Hurt
it.
But
I
heard
the
discussion
over
the
main
leads
the
the
the
the
none,
the
m2m
mapping
melted,
another
puzzle,
a
lot
and
the
memory
over
had
introduced
by
non
shared
hosting
that
it
is
not
isn't.
A
It
can
be
North
ignored,
so
I
think
the
the
one-to-one
mapping
the
benchmark
oval
of
a
mimetic
model
could
the
president
to
the
the
what
we
were
having
system
under
the
under
the
coder
is
simpler,
and
so,
even
if
we
we
found
that
we
need
to
switch
over
to
to
end
the
other.
We
don't
waste
a
lot
of
effort
devote
into
one
one
who
I'm
mapping.
D
Abstracting
the
difference
between
the
differences
between
Charlotte
and
not
Charlotte,
screams,
no
I,
just
well
I
started
from
create
from
abstracting
the
way.
How
we
create
messenger
then
moved
by
the
way.
How
we
create
monitor
client
then
also
make
some
simplifications
on
how
monitor
client
consume
messenger
before
it
was
just
Association.
D
A
A
B
A
A
We
can
put
it
into.
We
can
see
it
from
different
different
way.
If
a
service
is
charted,
it
could
choose
to
share
something
or
share
nothing
in
one-to-one
mapping
as
charged
a
shared
service
does
not
share
anything
in
what
is
this
share?
Is
a
status
to
take
a
type
I
will
just
started
service.
That's
all.
A
That's
why
what
I'm
kind
of
have
I'm
just
to
explain
that
we
wanted
to?
If
we
want
to
go
which
one
to
one
mapping,
we
need
to
remove
the
shared
a
structure
from
from,
for
example,
the
per
founder
or,
more
importantly,
configure
proxy,
so
it
won't,
it
will
be,
won't
want
to
share
anything
to
change
that
instance
of
our
config
proxy.
A
A
B
A
B
D
D
B
B
A
But
what
I'm
concerned
is
that
it's
if,
if
in
the
in
the
competition
between
the
C
star
D
and
if
the
sister
of
these
fails
to
the
competition
Whizzer
with
veloute,
we
cannot
just
put
that
it's
the
Tanakh
perform
the
world
because
a
criminal,
the
ability
have
more
course,
can
you
can
utilize
more
court.
Then
it's
not
affair.
A
D
D
B
D
B
A
There's
a
like
for
like
a
for
there's,
a
four
disks
or
for
object,
stores,
co-located
on
the
same
host.
We
can
start,
for
instance,
table
or
poor
or
different
crumbs,
devotee
and
Kingdom
240
from
the
course
and
get
adapt,
benchmark
results
and
the
and
then
on
the
very
same
host.
With
the
same
for
for
object
store.
We
we
can.
We
can
long
launch
our.
A
B
A
B
B
D
Felt
sure
I
thought
for
men,
sir,
there
is
basically
no
any
device
underneath
object.
Star
in
münster
is
an
extension
of
object,
store
that
resides
on
memory,
though,
basically
our
computation,
our
resources
are
just
a
few
power
and
available
memory.
Let's
say
we
will
got
notes,
we've
almost
indefinitely
of
memory
adores,
yes,.
B
B
A
B
A
A
Sorry,
the
Polti
put
up,
and
so
he
can
work
could
work
with
with
each
other
and
talk
talk
with
each
other
and
the
biggest
cover-up
I
discovered
by
the
monitor
and
be
able
to
talk
to
its
client.
That's
that's
why
I
think
one
of
the
four
most
important
task
is
to
to
get
in
the
boot
up
doctor
water,
I'm
working
on
and
the
second
thing
too,
since
we
are
working
on
the
master
branch,
we
need
to
address
the
interoperability
between
the
county,
monitor
and
the
London
master
branch
and
and
probably
manager.
B
A
A
A
B
A
D
B
A
B
D
We
could
just
abstract,
we
could
just
prepare
a
type
abstracting,
some
types
which
right
lock
like
itami,
the
atomic
like
all
that
stuff
and
stay
in
the
wrapper
that
for
the
prison
for
the
sister
built
the
mapping
is
to
is
just
education.
Of
course,
we
will
need
to
apply.
We
will
need
to
change
the
münster
itself
just
to
use
this
new
rap,
but
it
would
be
one-liner.
Basically,
you
are.
We
would
change
STD
atomic.
D
D
A
A
B
B
A
B
E
Yeah,
the
only
Tara
Dada
QT
32
Wii
system
message
improve
much
but
butter
for
other
QD
tests
that
the
performance
don't
don't--I,
change,
much
and
part
of
rope
and
a
barometer
hood
without
pressing
a
messenger.
It's
better
than
the
system
message,
because
butter
yeah,
because
because
other
question,
because
other
things
I
I
don't
do
performance
profile
suggested
by
the
readers
lawsuit
legasus
temple
are.
We
are
using
the
proper
and
and
the
work
located
up
to
the
performance
profile
and
the
suitor
returned.
E
E
B
B
E
B
E
E
A
E
C
E
A
D
D
D
Well,
guys,
I
think
that
we
really
need
I
would
prefer
to
not
spend
our
complexity
budget
on
the
very
beginning
of
the
project.
I
am
from
the
experience,
I
see,
the
things
are
evolving
and
the
complexity
is
growing.
If
we
start,
if
you
are,
if
you
will
start
from
something
that
is
already
very
complex
at
the
very
beginning,
the
complexity
will
be
ones
that
will
never
drop
in
in
the
future.
It
will
be
even
more
complex.
C
A
We
can
clients
yes,
currently
we
can
have
help,
have
the
kind
own
its
own
messenger
and
have
h
all
those
things
and
had
its
own
client,
but
but
I
need
to
I
need
to
point
out
that
the
account
messenger,
if
we
will
have
a
full-blown
crimson
OST,
each
OST,
will
be
talking
to
we're
reporting
to
the
major
and
the
client
and
messenger
will
be
responsible.
The
will
to
the
traffic
to
talk
into
a
messenger
manager.
C
A
A
D
D
C
C
D
The
moment,
if
it's
being
used,
it's
well,
let's
say
if
you,
if
you,
if,
if
your
method
is
taking
a
connect,
just
connection
reef
connection
ref
in
in
the
usage
of
it,
it's
like
current
and
if
we
are
switching.
However,
if
we
are
switching
connection
CrossRef,
then
you
need
to
do
something
like
that.
D
D
C
D
C
D
C
C
D
A
C
A
I
understand
correctly,
we
will.
We
also
apply
the
same
if
define
a
technique
to
to
to
the
dispatcher.
So
if
I
wanted
to
define
a
given,
the
other
subclass
satisficer
I,
probably
I,
will
inherit
from
the
foreign
dispatcher
if
we
call
with
M,
if,
if
the
with
T
star
singles,
that
is
not
defined.
Otherwise,
though
I
were
inherited
from
the
plane
plane
key
factor
is
that
right.
Well,.
A
C
D
A
A
Because
I
think
we
are,
we
can
just
have
it.
Actually,
we
have
a
lot
of
assumption
in
gear
and
it's
a
it's
a
it's
a
little
bit
complicated
under
it
because
of
our
hand.
We
are
preparing
for
one
went,
one
netting
went
to
m2
and
mapping
and
the
other
hand
we
are.
We
are
trying
to
get
to
the
have
a
lot
of
assumption
in
in
the
in
our
code
that
we
are.
We
believe
that
a
one-to-one
mapping
you're
simply
standard
and
probably
the
more
performant
like.
A
D
A
Discussed
the
distr
district
I've
discussed
this
under,
have
a
total
council
town
and
one
to
one
mapping,
at
least
for
the
short
term,
to
get
up
get
a
number
to
ensure
that
we
are
honored
or
to
verify
that
our
idea
is
is
read
right
or
wrong
in
the
world
case
it
we
should
not,
should
abandon
the
ship
and
the
path
case.
The
way
we
we
know,
that
is
a
it's
performed
very
good,
and
we
should
go
this
way.
D
Yeah
that
sounds
reasonable
by
the
way
I
in
the
discussion
on
that
sub
level.
I'm
also
a
lot
of
that
we
basically
haven't
defined
the
scope
for
the
world
product
and
people
are
mixed.
Some
different
problems,
yes,
I,
think
I
personally
think
about
the
Crimson
OSD,
just
like
Roger
small
product
consume
very
fast
devices,
but
I
stopped
I
started.
Think
people
are
also
thinking
about
bringing
much
more
devices
much
more
disks,
but
more
storage
2x
to
the
whole
project.
A
A
A
D
Is
is
thinking
about
very
beefy,
very
white
OSD.
It
has
some
nice
benefit
of
reducing
the
number
of
OSD
instances
you
would
need
to
to
deploy
on
a
given
set
of
of
couple
of
storage
capacity.
It
means
it
also
way.
We
would
also
minimize
the
pressure
on
our
radios
infrastructure
on
the
OSD
map
size.
That's
a
threat
at
basic
things,
I
think
it's
a
different
problem.
D
We
are
mixing
it's
very
fundamental
one,
whether
we
have
the
crash
capacity
cap,
the
crash
capacity,
whether
we
have
the
radius
capacity
but
I
belt
I,
believe
they
are
orthogonal
to
the
criminal.
The
sole
junction
point
between
efficient
single
device,
conservation
device,
consumption
and
radius
capacity
is
that
tom
is
that
Tom.
D
A
A
C
C
A
C
C
C
C
C
Think
so,
because
all
the
connections
are
shattered
by
peer
IP
and
they
they
all
have
the
thing
apiece
or
all
the
connections
in
in
the
shard.
A
the
messenger
in
tests
are
actually
Ronnie
in
the
same
core
and
they
still
have
this
issue.
That's
why
I
think
it
is
related
to
the
one
derided
for
ste
and
the
messenger.
C
C
A
C
C
B
A
D
I
think
a
couple
of
possible
items
we
need
to
have
the
fertilized
object
star.
We
also
need
to
slightly
out,
and
we
also
need
to
bring
the
fertilized
mammoth
star
and
finally,
glow
the
manager
history
glue,
the
messenger
and
the
dispatch
loud
logic
to
object
star.
Basically,
it's
the
rich
I
hope
our.
D
Fertilized
object,
star
is
just
the
interface
the
food
to
rice,
ma'am
star
would
inherit
from
publicly
inherit
from
it
will
implement
basically,
but
the
footrest
MEMS
would
basically
use
multiple
inheritance,
private
inhale.
It
will
privately
inherit
my
current
münster
just
to
claim
for
the
current
implementation
we
have
and
secondary.
It
would
also
it
would
publicly
inherit
I
mean
implement
the
fertilized
object,
star.
D
A
A
B
D
B
A
B
D
I
expect
in
the
future
we'll
have
close
future.
We
get
three
different
implementations
of
the
future
objects
during
the
first.
The
one,
possibly
one
is
the
adapter
concept
from
future
eyes.
Objects
turn
to
object
star
using
a
fret
bull.
Second,
one
is
just
for
testing
the
Futurist
mem
star,
possibly.