All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Dragos Tatulea <dtatulea@nvidia.com>,
	linux-rdma@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH rdma-rc v1] IB/IPoIB: Fix legacy IPoIB due to wrong number of queues
Date: Tue, 24 Jan 2023 08:27:09 +0200	[thread overview]
Message-ID: <Y896PRioqqz6nVCZ@unreal> (raw)
In-Reply-To: <Y87SpbbdYE3A+y46@nvidia.com>

On Mon, Jan 23, 2023 at 02:32:05PM -0400, Jason Gunthorpe wrote:
> On Sun, Jan 22, 2023 at 02:44:35PM +0200, Leon Romanovsky wrote:
> 
> > > And the return of a really big number from ops->get_num_rx_queues is
> > > pretty ugly too, ideally that would be fixed to pass in some function
> > > arguments and obtain the ppriv so it can return the actual maximum
> > > number of queues and we don't waste a bunch of memory..
> > 
> > .get_num_rx_queues() is declared as void, so it can't have any complex
> > logic except returns some global define.
> 
> Well, yes, you'd have to add some arguments..

Jason, please be realistic.

We already were in this place, where we wanted to change netdev stack
for our IPoIB deadlock. As you probably remember, that didn't went well.

I see a little value to change bunch of netdev drivers just to save some
bytes in legacy IPoIB.

Thanks

>  
> Jason

  reply	other threads:[~2023-01-24  6:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 17:02 [PATCH rdma-rc v1] IB/IPoIB: Fix legacy IPoIB due to wrong number of queues Leon Romanovsky
2023-01-20 20:52 ` Jason Gunthorpe
2023-01-21  8:40   ` Dragos Tatulea
2023-01-22 12:44   ` Leon Romanovsky
2023-01-23 18:32     ` Jason Gunthorpe
2023-01-24  6:27       ` Leon Romanovsky [this message]
2023-01-24 13:00         ` Jason Gunthorpe

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=Y896PRioqqz6nVCZ@unreal \
    --to=leon@kernel.org \
    --cc=dtatulea@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=tariqt@nvidia.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.