From: Cristian Zamfir <zamf@dcs.gla.ac.uk>
To: xen-devel@lists.xensource.com
Subject: arp during live migration
Date: Fri, 02 Mar 2007 20:54:02 +0000 [thread overview]
Message-ID: <45E88EEA.4020707@dcs.gla.ac.uk> (raw)
Hi,
I am having some trouble with the send_fake_arp in the netfront driver.
Normally, on my domU, which has no queuing disciplines compiled in, the
packets are sent via dev_queue_xmit in net/core/dev.c and enqueued using
pfifo_fast_enqueue in net/sched/sch_generic.c.
However, during live migration, send_fake_arp() returns -2 and does not
go to pfifo_fast_enqueue any more. I have been able to trace it further
than this code in dev_queue_xmit:
if (q->enqueue) {
/* Grab device queue */
spin_lock(&dev->queue_lock);
rc = q->enqueue(skb, q);
qdisc_run(dev);
spin_unlock(&dev->queue_lock);
rc = rc == NET_XMIT_BYPASS ? NET_XMIT_SUCCESS : rc;
goto out;
}
I noticed that the error code returned by send_fake_arp() is not
checked. Would it be a good option to check the error code and
reschedule the arp broadcast at a later time?
I have made some changes to xen 3.0.3 regarding block device migration
so I might have messed things up. It could be the reason only few people
reported this problem on xen-users. Obviously, the problem can also go
unnoticed if a downtime of 1-2 seconds is tolerated.
Does anyone have any hints on why this might happen or how to search for
more clues?
Thank you.
Cristian
next reply other threads:[~2007-03-02 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 20:54 Cristian Zamfir [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-02 22:22 arp during live migration Graham, Simon
2007-03-03 16:21 ` Jacob Gorm Hansen
2007-03-03 17:10 ` Graham, Simon
2007-03-05 15:40 ` Cristian Zamfir
[not found] ` <1172938895.14470.25.ca mel@localhost.localdomain>
2007-03-05 23:47 ` Graham, Simon
2007-03-06 22:59 ` Graham, Simon
2007-03-07 8:30 ` Keir Fraser
2007-03-07 16:02 ` Keir Fraser
2007-03-07 22:25 ` Graham, Simon
2007-03-08 7:53 ` Keir Fraser
2008-01-30 11:17 ` Hans-Christian Armingeon
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45E88EEA.4020707@dcs.gla.ac.uk \
--to=zamf@dcs.gla.ac.uk \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.