netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Sainath Grandhi <sainath.grandhi@intel.com>
Cc: netdev <netdev@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	mahesh@bandewar.net,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv1 5/7] TAP: Extending tap device create/destroy APIs
Date: Sat, 7 Jan 2017 01:20:48 +0200	[thread overview]
Message-ID: <CAHp75VcEquDVRA4yNSh4pxczc60=+fdFkeG4Cji1patZYUk6xw@mail.gmail.com> (raw)
In-Reply-To: <1483742009-19184-6-git-send-email-sainath.grandhi@intel.com>

On Sat, Jan 7, 2017 at 12:33 AM, Sainath Grandhi
<sainath.grandhi@intel.com> wrote:
> Extending tap APIs get/free_minor and create/destroy_cdev to handle more than one
> type of virtual interface.
>
> Signed-off-by: Sainath Grandhi <sainath.grandhi@intel.com>
> Tested-by: Sainath Grandhi <sainath.grandhi@intel.com>

Usually it implies that commiter has tested the stuff.

> --- a/drivers/net/tap.c
> +++ b/drivers/net/tap.c
> @@ -99,12 +99,16 @@ static struct proto tap_proto = {
>  };
>
>  #define TAP_NUM_DEVS (1U << MINORBITS)

> +
> +LIST_HEAD(major_list);
> +

static ?

> -int tap_get_minor(struct tap_dev *tap)
> +int tap_get_minor(dev_t major, struct tap_dev *tap)
>  {
>         int retval = -ENOMEM;
> +       struct major_info *tap_major, *tmp;
> +       bool found = false;
>
> -       mutex_lock(&macvtap_major.minor_lock);
> -       retval = idr_alloc(&macvtap_major.minor_idr, tap, 1, TAP_NUM_DEVS, GFP_KERNEL);

> +       list_for_each_entry_safe(tap_major, tmp, &major_list, next) {
> +               if (tap_major->major == MAJOR(major)) {
> +                       found = true;
> +                       break;
> +               }
> +       }
> +
> +       if (!found)
> +               return -EINVAL;

This is candidate to be a separate helper function. See also below.


> -void tap_free_minor(struct tap_dev *tap)
> +void tap_free_minor(dev_t major, struct tap_dev *tap)
>  {
> -       mutex_lock(&macvtap_major.minor_lock);
> +       struct major_info *tap_major, *tmp;

> +       bool found = false;
> +
> +       list_for_each_entry_safe(tap_major, tmp, &major_list, next) {
> +               if (tap_major->major == MAJOR(major)) {
> +                       found = true;
> +                       break;
> +               }
> +       }
> +
> +       if (!found)
> +               return;

Here is quite the same code (as above).

> -static struct tap_dev *dev_get_by_tap_minor(int minor)
> +static struct tap_dev *dev_get_by_tap_file(int major, int minor)
>  {
>         struct net_device *dev = NULL;
>         struct tap_dev *tap;
> +       struct major_info *tap_major, *tmp;
> +       bool found = false;
>
> -       mutex_lock(&macvtap_major.minor_lock);
> -       tap = idr_find(&macvtap_major.minor_idr, minor);

> +       list_for_each_entry_safe(tap_major, tmp, &major_list, next) {
> +               if (tap_major->major == major) {
> +                       found = true;
> +                       break;
> +               }
> +       }
> +
> +       if (!found)
> +               return NULL;

And here.

> +static int tap_list_add(dev_t major, const char *device_name)
> +{

> +       int err = 0;
> +       struct major_info *tap_major;

Perhaps
+       struct major_info *tap_major;
+       int err = 0;

> +
> +       tap_major = kzalloc(sizeof(*tap_major), GFP_ATOMIC);
> +
> +       tap_major->major = MAJOR(major);
> +
> +       idr_init(&tap_major->minor_idr);
> +       mutex_init(&tap_major->minor_lock);
> +
> +       tap_major->device_name = device_name;
> +
> +       list_add_tail(&tap_major->next, &major_list);
> +       return err;


> +       err = tap_list_add(*tap_major, device_name);
>
>         return err;

return tap_list_add();

>  void tap_destroy_cdev(dev_t major, struct cdev *tap_cdev)
>  {
> +       struct major_info *tap_major, *tmp;
> +       bool found = false;
> +
> +       list_for_each_entry_safe(tap_major, tmp, &major_list, next) {
> +               if (tap_major->major == MAJOR(major)) {
> +                       found = true;
> +                       break;
> +               }
> +       }
> +
> +       if (!found)
> +               return;

And here.

-- 
With Best Regards,
Andy Shevchenko

  parent reply	other threads:[~2017-01-06 23:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 22:33 [PATCHv1 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces Sainath Grandhi
2017-01-06 22:33 ` [PATCHv1 1/7] TAP: Refactoring macvtap.c Sainath Grandhi
2017-01-06 23:12   ` Andy Shevchenko
2017-01-06 22:33 ` [PATCHv1 2/7] TAP: Renaming tap related APIs, data structures, macros Sainath Grandhi
2017-01-07 10:44   ` kbuild test robot
2017-01-07 12:00   ` kbuild test robot
2017-01-06 22:33 ` [PATCHv1 3/7] TAP: Tap character device creation/destroy API Sainath Grandhi
2017-01-06 22:33 ` [PATCHv1 4/7] TAP: Abstract type of virtual interface from tap implementation Sainath Grandhi
2017-01-06 22:33 ` [PATCHv1 5/7] TAP: Extending tap device create/destroy APIs Sainath Grandhi
2017-01-06 23:15   ` Eric Dumazet
2017-01-17 23:07     ` Grandhi, Sainath
2017-01-06 23:20   ` Andy Shevchenko [this message]
2017-01-17 23:51     ` Grandhi, Sainath
2017-01-06 22:33 ` [PATCHv1 6/7] TAP: tap as an independent module Sainath Grandhi
2017-01-07 10:46   ` kbuild test robot
2017-01-07 12:32   ` kbuild test robot
2017-01-06 22:33 ` [PATCHv1 7/7] IPVTAP: IP-VLAN based tap driver Sainath Grandhi
2017-01-06 23:14   ` Eric Dumazet
2017-01-17 23:06     ` Grandhi, Sainath
2017-01-06 23:46   ` Mahesh Bandewar (महेश बंडेवार)
2017-01-17 23:49     ` Grandhi, Sainath

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='CAHp75VcEquDVRA4yNSh4pxczc60=+fdFkeG4Cji1patZYUk6xw@mail.gmail.com' \
    --to=andy.shevchenko@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahesh@bandewar.net \
    --cc=netdev@vger.kernel.org \
    --cc=sainath.grandhi@intel.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).