All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, Matthieu Ternisien d'Ouville <matthieu.tdo@6wind.com>
Subject: Re: [PATCH] net/mlx: remove link update lock
Date: Mon, 16 Jan 2017 15:03:23 +0100	[thread overview]
Message-ID: <20170116140323.GD3779@6wind.com> (raw)
In-Reply-To: <1484153041-18034-1-git-send-email-olivier.matz@6wind.com>

On Wed, Jan 11, 2017 at 05:44:01PM +0100, Olivier Matz wrote:
> From: Matthieu Ternisien d'Ouville <matthieu.tdo@6wind.com>
> 
> Retrieving link status information through the link update callback should
> be quick and non-blocking.
> 
> Mellanox PMDs retrieve this information through ioctl() calls on the
> related kernel netdevice. This appears to take a long time to
> complete and may cause significant slowdowns in applications.
> 
> While these system calls cannot be accelerated, removing the lock on the
> private structure allows applications to perform other control operations
> from separate threads in the meantime. This function remains safe without
> locking as it does not write the private structure, it is only used to
> retrieve the name of the netdevice.
> 
> Signed-off-by: Matthieu Ternisien d'Ouville <matthieu.tdo@6wind.com>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
> ---
>  drivers/net/mlx4/mlx4.c        | 32 ++++++--------------------------
>  drivers/net/mlx5/mlx5.c        |  2 +-
>  drivers/net/mlx5/mlx5.h        |  1 -
>  drivers/net/mlx5/mlx5_ethdev.c | 30 ++++++------------------------
>  4 files changed, 13 insertions(+), 52 deletions(-)

Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2017-01-16 14:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 16:44 [PATCH] net/mlx: remove link update lock Olivier Matz
2017-01-16 14:03 ` Adrien Mazarguil [this message]
2017-01-16 17:19   ` Ferruh Yigit

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=20170116140323.GD3779@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=matthieu.tdo@6wind.com \
    --cc=olivier.matz@6wind.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 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.