AsyncMessenger maturity

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi All,

I tried to evaluate AsyncMessenger (together with its sub classes) and I found its code great in my eyes. Still, when using it at runtime, Ceph will warn you that this module is dangerous.

*I have two questions:*
1. Considering pros and cons, are there any cons when using AsyncMessenger instead of SimpleMessenger (like stability, or cpu/memory consumption, .)

2. I am considering a variant of AsyncMessenger that might require that both sides will be same messenger, I wonder, is it possible to use AsyncMessenger for private network between OSDs only and to remain with SimpleMessenger for all other messengers (for example, by just changing the lines that creates the 6 Messengers in ceph_osd.cc::main) 

TIA,
  Avner

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux