From: David Miller <davem@davemloft.net>
To: robert@herjulf.net
Cc: eric.dumazet@gmail.com, robert.olsson@its.uu.se,
netdev@vger.kernel.org, shemminger@vyatta.com
Subject: Re: [PATCH] pktgen: Fix multiqueue handling
Date: Sun, 04 Oct 2009 21:09:23 -0700 (PDT) [thread overview]
Message-ID: <20091004.210923.82587218.davem@davemloft.net> (raw)
In-Reply-To: <19143.42215.379289.481809@gargle.gargle.HOWL>
From: Robert Olsson <robert@herjulf.net>
Date: Sat, 3 Oct 2009 21:24:23 +0200
>
>
> Thanks yes is seems right. We can chose a single arbitrary TX queue with the patch.
> BTW Noticed you and Stephen discussed to reduce dirtying skb->users, maybe the idea
> to bump up skb->users to clone_skb is not so bad. I'll think the code will be pretty
> straight-forward.
>
> Cheers
> --ro
>
>
> Signed-off-by: Robert Olsson <robert.olsson@its.uu.se>
Applied, thanks everyone.
prev parent reply other threads:[~2009-10-05 4:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 6:24 [PATCH] pktgen: Fix multiqueue handling Eric Dumazet
2009-10-03 19:24 ` Robert Olsson
2009-10-05 4:09 ` David Miller [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=20091004.210923.82587218.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=robert.olsson@its.uu.se \
--cc=robert@herjulf.net \
--cc=shemminger@vyatta.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 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).