From: Mark McLoughlin <markmc@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: netdev@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 3/4] virtio_net: don't free buffers in xmit ring
Date: Tue, 02 Jun 2009 12:41:42 +0100 [thread overview]
Message-ID: <1243942902.9146.216.camel@blaa> (raw)
In-Reply-To: <1243930422.9146.60.camel@blaa>
On Tue, 2009-06-02 at 09:13 +0100, Mark McLoughlin wrote:
> On Fri, 2009-05-29 at 23:46 +0930, Rusty Russell wrote:
> > The virtio_net driver is complicated by the two methods of freeing old
> > xmit buffers (in addition to freeing old ones at the start of the xmit
> > path).
> >
> > The original code used a 1/10 second timer attached to xmit_free(),
> > reset on every xmit. Before we orphaned skbs on xmit, the
> > transmitting userspace could block with a full socket until the timer
> > fired, the skb destructor was called, and they were re-woken.
>
> The timer was actually added to solve a hang when trying to unload
> nf_conntrack AFAIR - nf_conntrack was blocking on the skb being freed
> and we never actually freed it.
>
> I think skb_orphan() is enough to prevent this, is it?
Oops, I meant:
I don't think skb_orphan() is enough to prevent this, is it?
Cheers,
Mark.
next prev parent reply other threads:[~2009-06-02 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 14:16 [PATCH 3/4] virtio_net: don't free buffers in xmit ring Rusty Russell
2009-06-02 8:13 ` Mark McLoughlin
2009-06-02 11:41 ` Mark McLoughlin [this message]
2009-06-02 14:07 ` Rusty Russell
2009-06-02 14:07 ` Rusty Russell
2009-06-02 11:41 ` Mark McLoughlin
2009-06-02 13:43 ` Rusty Russell
2009-06-02 13:43 ` Rusty Russell
2009-06-02 8:13 ` Mark McLoughlin
-- strict thread matches above, loose matches on Subject: below --
2009-05-29 14:16 Rusty Russell
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=1243942902.9146.216.camel@blaa \
--to=markmc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.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 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.