From: Mulyadi Santosa <a_mulyadi@softhome.net>
To: qemu-devel@nongnu.org, "Jim C. Brown" <jma5@umd.edu>
Subject: Re: [Qemu-devel] vde-inject 0.0.1
Date: Fri, 10 Feb 2006 12:34:10 +0700 [thread overview]
Message-ID: <200602101234.10853.a_mulyadi@softhome.net> (raw)
In-Reply-To: <20060209053953.GA13800@jbrown.mylinuxbox.org>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
Hi Jim
It's me again. here I send you another patch for the vde_pcap_inject.c.
Nothing fancy here, I only did:
- move out "open" and "close" from relay() and put them on main()
before entering for() loop. IMHO, this will make file operation a bit
faster
- I use __builtin_expect magic to optimize the "if" condition before
writing to /proc/vdeinject. here, inside relay() we assume that
vdeinject is likely exist.
PS: I can't check it thoroughly since my libpcap version (0.7.2, default
on Redhat 9. Yes I know it is old) doesn't have
pcap_get_selectable_fd(), so I can't compile it.
regards
Mulyadi
[-- Attachment #2: vde_pcap_inject.zip --]
[-- Type: application/x-zip, Size: 740 bytes --]
next prev parent reply other threads:[~2006-02-10 5:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 23:13 [Qemu-devel] vde-inject 0.0.0 Jim C. Brown
2006-02-09 5:39 ` [Qemu-devel] vde-inject 0.0.1 Jim C. Brown
2006-02-09 18:23 ` Mulyadi Santosa
2006-02-10 5:34 ` Mulyadi Santosa [this message]
2006-02-10 17:09 ` Jim C. Brown
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=200602101234.10853.a_mulyadi@softhome.net \
--to=a_mulyadi@softhome.net \
--cc=jma5@umd.edu \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).