From: Jason Wang <jasowang@redhat.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: davem@davemloft.net, mst@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next RFC 3/8] macvtap: introduce macvtap_get_vlan()
Date: Fri, 24 May 2013 14:21:12 +0800 [thread overview]
Message-ID: <519F06D8.6030605@redhat.com> (raw)
In-Reply-To: <519E318B.2010804@cogentembedded.com>
On 05/23/2013 11:11 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 23-05-2013 7:12, Jason Wang wrote:
>
>> Factor out the device holding logic to a macvtap_get_vlan(), this
>> will be also
>> used by multiqueue API.
>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> ---
>> drivers/net/macvtap.c | 26 +++++++++++++++++++-------
>> 1 files changed, 19 insertions(+), 7 deletions(-)
>
>> diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
>> index ce1c72a..a36e49e 100644
>> --- a/drivers/net/macvtap.c
>> +++ b/drivers/net/macvtap.c
>> @@ -890,6 +890,23 @@ out:
>> return ret;
>> }
>>
>> +static struct macvlan_dev *macvtap_get_vlan(struct macvtap_queue *q)
>> +{
>> + struct macvlan_dev *vlan;
>
> Empty line wouldn't hurt here, after declaration.
Will add one line here. Thanks
>
>> + rcu_read_lock_bh();
>> + vlan = rcu_dereference_bh(q->vlan);
>> + if (vlan)
>> + dev_hold(vlan->dev);
>> + rcu_read_unlock_bh();
>> +
>> + return vlan;
>> +}
> [...]
>
> WBR, Sergei
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-05-24 6:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 3:12 [net-next RFC 0/8] multiqueue API support for macvtap Jason Wang
2013-05-23 3:12 ` [net-next RFC 1/8] macvlan: switch to use IS_ENABLED() Jason Wang
2013-05-23 11:31 ` Michael S. Tsirkin
2013-05-23 3:12 ` [net-next RFC 2/8] macvtap: return -EBADFD when TUNGETIFF fails Jason Wang
2013-05-23 11:54 ` Michael S. Tsirkin
2013-05-24 6:28 ` Jason Wang
2013-05-23 3:12 ` [net-next RFC 3/8] macvtap: introduce macvtap_get_vlan() Jason Wang
2013-05-23 15:11 ` Sergei Shtylyov
2013-05-24 6:21 ` Jason Wang [this message]
2013-05-23 3:12 ` [net-next RFC 4/8] macvlan: reduce the max number of taps to 8 Jason Wang
2013-05-23 6:37 ` Michael S. Tsirkin
2013-05-24 5:14 ` Jason Wang
2013-05-23 3:12 ` [net-next RFC 5/8] macvtap: eliminate linear search Jason Wang
2013-05-23 11:41 ` Michael S. Tsirkin
2013-05-24 5:33 ` Jason Wang
2013-05-23 3:12 ` [net-next RFC 6/8] macvtap: allow TUNSETIFF to create multiqueue device Jason Wang
2013-05-23 11:45 ` Michael S. Tsirkin
2013-05-24 5:36 ` Jason Wang
2013-05-23 3:12 ` [net-next RFC 7/8] macvtap: add TUNSETQUEUE ioctl Jason Wang
2013-05-23 11:52 ` Michael S. Tsirkin
2013-05-24 6:19 ` Jason Wang
2013-05-23 3:12 ` [net-next RFC 8/8] macvtap: enable multiqueue flag Jason Wang
2013-05-23 11:53 ` [net-next RFC 0/8] multiqueue API support for macvtap Michael S. Tsirkin
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=519F06D8.6030605@redhat.com \
--to=jasowang@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).