From: David Miller <davem@davemloft.net>
To: sysoleg@yandex.ru
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6 2/2] mq: preserve queue mapping with bonding and VLAN devices
Date: Sun, 28 Feb 2010 01:33:11 -0800 (PST) [thread overview]
Message-ID: <20100228.013311.242139140.davem@davemloft.net> (raw)
In-Reply-To: <272541267277332@webmail86.yandex.ru>
From: "\"Oleg A. Arkhangelsky\"" <sysoleg@yandex.ru>
Date: Sat, 27 Feb 2010 16:28:52 +0300
> Forwarded packet goes through dev_queue_xmit() more that once
> when using bonding or 802.1q VLAN devices, so we've lost rx-tx
> queue mapping index for real devices. This is because initial
> queue index value (as it recorded by skb_record_tx_queue()) is
> overwritten by skb_set_queue_mapping().
>
> Signed-off-by: Oleg A. Arkhangelsky <sysoleg@yandex.ru>
Applied, thanks Oleg.
Patch #1 still needs work, please address Eric Dumazet's feedback.
Thanks!
next prev parent reply other threads:[~2010-02-28 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 13:28 [PATCH net-next-2.6 2/2] mq: preserve queue mapping with bonding and VLAN devices "Oleg A. Arkhangelsky"
2010-02-28 9:33 ` David Miller [this message]
2010-02-28 9:36 ` David Miller
2010-02-28 11:35 ` "Oleg A. Arkhangelsky"
2010-03-01 2:45 ` David Miller
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=20100228.013311.242139140.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sysoleg@yandex.ru \
/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).