mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2025-02-21 19:02:30 +00:00
virtio-device: fix some misspelled words in comment
Fix some trivial spelling problem. No functional change. Signed-off-by: Yi Wang <wang.yi59@zte.com.cn>
This commit is contained in:
parent
c439324451
commit
1adcf5225b
@ -70,7 +70,7 @@ impl ConsoleEpollHandler {
|
||||
/*
|
||||
* Each port of virtio console device has one receive
|
||||
* queue. One or more empty buffers are placed by the
|
||||
* dirver in the receive queue for incoming data. Here,
|
||||
* driver in the receive queue for incoming data. Here,
|
||||
* we place the input data to these empty buffers.
|
||||
*/
|
||||
fn process_input_queue(&mut self) -> bool {
|
||||
|
@ -261,7 +261,7 @@ impl VirtioCommon {
|
||||
|
||||
if queues.len() < self.min_queues.into() {
|
||||
error!(
|
||||
"Number of enabled queues lower tham min: {} vs {}",
|
||||
"Number of enabled queues lower than min: {} vs {}",
|
||||
queues.len(),
|
||||
self.min_queues
|
||||
);
|
||||
|
@ -51,7 +51,6 @@ pub struct Net {
|
||||
}
|
||||
|
||||
impl Net {
|
||||
/// Create a new vhost-user-net device
|
||||
/// Create a new vhost-user-net device
|
||||
pub fn new(
|
||||
id: String,
|
||||
|
@ -54,7 +54,7 @@
|
||||
// 3. Flow control
|
||||
// Before sending a data packet (VSOCK_OP_RW), the sender must make sure that the receiver
|
||||
// has enough free buffer space to store that data. If this condition is not respected, the
|
||||
// receiving peer's behaviour is undefined. In this implementation, we forcefully terminate
|
||||
// receiving peer's behavior is undefined. In this implementation, we forcefully terminate
|
||||
// the connection by sending back a VSOCK_OP_RST packet.
|
||||
// Note: all buffer space information is computed and stored on a per-connection basis.
|
||||
// Peers keep each other informed about the free buffer space they have by filling in two
|
||||
@ -197,7 +197,7 @@ where
|
||||
}
|
||||
|
||||
// Oh wait, before we start bringing in the big data, can our peer handle receiving so
|
||||
// much bytey goodness?
|
||||
// much bytes goodness?
|
||||
if self.need_credit_update_from_peer() {
|
||||
self.last_fwd_cnt_to_peer = self.fwd_cnt;
|
||||
pkt.set_op(uapi::VSOCK_OP_CREDIT_REQUEST);
|
||||
|
@ -213,7 +213,7 @@ impl Watchdog {
|
||||
self.common.avail_features = state.avail_features;
|
||||
self.common.acked_features = state.acked_features;
|
||||
// When restoring enable the watchdog if it was previously enabled. We reset the timer
|
||||
// to ensure that we don't unnecesarily reboot due to the offline time.
|
||||
// to ensure that we don't unnecessarily reboot due to the offline time.
|
||||
if state.enabled {
|
||||
self.last_ping_time.lock().unwrap().replace(Instant::now());
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user