From: "Michael S. Tsirkin" <mst@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: netdev@vger.kernel.org, Patrick McHardy <kaber@trash.net>,
Stephen Hemminger <shemminger@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
Or Gerlitz <ogerlitz@voltaire.com>,
"Fischer, Anna" <anna.fischer@hp.com>,
bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Edge Virtual Bridging <evb@yahoogroups.com>
Subject: Re: [PATCH] macvlan: add tap device backend
Date: Mon, 10 Aug 2009 16:42:29 +0300 [thread overview]
Message-ID: <20090810134229.GA10036@redhat.com> (raw)
In-Reply-To: <200908101529.46285.arnd@arndb.de>
On Mon, Aug 10, 2009 at 03:29:46PM +0200, Arnd Bergmann wrote:
> On Monday 10 August 2009, Michael S. Tsirkin wrote:
> >
> > > Would it be enough to check the dev_queue_xmit() return
> > > code for NETDEV_TX_BUSY?
> > >
> > > How would I get notified when it gets free again?
> >
> > You can do this by creating a socket. Look at how tun does
> > this now.
>
> Hmm, I was hoping to be able to avoid this, because I can
> interact more directly with the outbound physical interface
> using dev_queue_xmit() instead of netif_rx_ni().
Yea, that's what tun does. socket just notifies you when
packets are freed.
> I'll have a look. Thanks,
>
> Arnd <><
next prev parent reply other threads:[~2009-08-10 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 21:50 [PATCH] macvlan: add tap device backend Arnd Bergmann
2009-08-07 3:20 ` David Miller
2009-08-07 17:35 ` [Bridge] " Daniel Robbins
2009-08-09 8:02 ` Michael S. Tsirkin
2009-08-09 20:42 ` Arnd Bergmann
2009-08-10 8:50 ` Michael S. Tsirkin
2009-08-10 13:29 ` Arnd Bergmann
2009-08-10 13:42 ` Michael S. Tsirkin [this message]
2009-08-10 6:47 ` Patrick McHardy
2009-08-10 18:43 ` Arnd Bergmann
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=20090810134229.GA10036@redhat.com \
--to=mst@redhat.com \
--cc=anna.fischer@hp.com \
--cc=arnd@arndb.de \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=evb@yahoogroups.com \
--cc=herbert@gondor.apana.org.au \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.com \
--cc=shemminger@linux-foundation.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).