From: "Steve Schmidtke" <steve_schmidtke@hotmail.com>
To: kraxel@bytesex.org
Cc: User-mode-linux-devel@lists.sourceforge.net, uml@uxu.ch
Subject: [uml-devel] Re: [PATCH] uml_router: cleanup #2
Date: Tue, 30 Nov 2004 17:44:53 +0000 [thread overview]
Message-ID: <BAY24-F272A756C4E6200D477EB2F83BE0@phx.gbl> (raw)
In-Reply-To: <20041130103255.GB5593@bytesex>
Gerd Knorr wrote:
> > Patch 11 turns on the packet queue for the tuntap driver. For technical
> > reasons, it's just too much work to implement on the current sockunix
> > driver.
>Guess thats the "one socket for all umls" thingy?
Yup, I now see what you mean by broken by design. :) I think it is possible
to do, but just not worth the effort or complexity when...
>You can create a new
>socket for every uml instance connecting, at least with protocol v3 (not
>sure about the older ones, but I think support for them can be dropped
>without breaking anything by now ...).
Your socket driver looks perfect for the job. I think Jeff would be happy
if both could run side by side.
Steve Schmidtke
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-11-30 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 5:11 [uml-devel] [PATCH] uml_router: cleanup #2 Steve Schmidtke
2004-11-30 10:32 ` [uml-devel] " Gerd Knorr
2004-11-30 13:27 ` Blaisorblade
2004-11-30 17:51 ` Steve Schmidtke
2004-11-30 17:44 ` Steve Schmidtke [this message]
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=BAY24-F272A756C4E6200D477EB2F83BE0@phx.gbl \
--to=steve_schmidtke@hotmail.com \
--cc=User-mode-linux-devel@lists.sourceforge.net \
--cc=kraxel@bytesex.org \
--cc=uml@uxu.ch \
/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