netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Petko Manolov <petkan@nucleusys.com>
Cc: "Greg KH" <greg@kroah.com>, "Ben Hutchings" <ben@decadent.org.uk>,
	netdev@vger.kernel.org, linux-usb@vger.kernel.org,
	"Lisandro Damián Nicanor Pérez Meyer" <lisandro@debian.org>
Subject: Re: [PATCH net 1/4] pegasus: Use heap buffers for all register access
Date: Mon, 6 Feb 2017 14:21:24 +0100	[thread overview]
Message-ID: <20170206132124.GA3038@localhost> (raw)
In-Reply-To: <20170206125108.d5vdur5rlvrkpr5j@localhost>

On Mon, Feb 06, 2017 at 02:51:09PM +0200, Petko Manolov wrote:
> On 17-02-06 09:28:22, Greg KH wrote:
> > On Mon, Feb 06, 2017 at 10:14:44AM +0200, Petko Manolov wrote:

> > > Random thought: isn't it better to add the alloc/free code in 
> > > usb_control_msg() and avoid code duplication all over the driver space?
> > 
> > A very long time ago we considered it, but realized that the majority of 
> > drivers already had the memory dynamically allocated, so we just went with 
> > this.  Perhaps we could revisit that if it turns out we were wrong, and would 
> > simplify things.
> 
> A quick glance at usb_control_msg() users (looked only at .../net/usb and 
> .../usb/serial) shows that most of them have the buffer allocated in stack.  

That's simply not true at all for usb-serial. If you find an instance
were a stack allocated buffer is used for DMA that hasn't yet been
fixed in USB serial, then please point it out so we can fix it up (I
doubt you'll find one, though).

> These transfers are relatively infrequent and quite small the performance hit 
> caused by memcpy() should also be negligible.

Note that some drivers allocate a single buffer which is reused for
several (or all) control transfers.

Johan

  reply	other threads:[~2017-02-06 13:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-04 16:54 [PATCH net 0/4] Fix on-stack USB buffers Ben Hutchings
2017-02-04 16:56 ` [PATCH net 1/4] pegasus: Use heap buffers for all register access Ben Hutchings
2017-02-05  0:30   ` Greg KH
2017-02-06  8:14     ` Petko Manolov
2017-02-06  8:28       ` Greg KH
2017-02-06 12:51         ` Petko Manolov
2017-02-06 13:21           ` Johan Hovold [this message]
2017-02-06 13:32             ` Johan Hovold
2017-02-06 13:46               ` Johan Hovold
2017-02-07 10:24                 ` Petko Manolov
2017-02-07 10:45                   ` Greg KH
     [not found]                     ` <20170207104506.GB32583-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-02-07 12:50                       ` Petko Manolov
2017-02-06 13:30           ` David Laight
2017-02-07 18:32           ` Steve Calfee
2017-02-08  7:57             ` Petko Manolov
2017-02-04 16:56 ` [PATCH net 2/4] rtl8150: " Ben Hutchings
2017-02-06  8:10   ` Petko Manolov
     [not found]   ` <20170204165631.GW3442-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
2017-02-06 16:09     ` David Laight
2017-02-06 16:25       ` Ben Hutchings
2017-02-07 10:34         ` Petko Manolov
2017-02-07 10:51           ` Greg KH
2017-02-07 11:56             ` David Laight
     [not found]               ` <063D6719AE5E284EB5DD2968C1650D6DB027DB75-VkEWCZq2GCInGFn1LkZF6NBPR1lH4CV8@public.gmane.org>
2017-02-07 12:42                 ` 'Greg KH'
2017-02-07 12:53             ` Petko Manolov
2017-02-07 13:01               ` Greg KH
2017-02-07 13:20                 ` Petko Manolov
2017-02-07 14:14                   ` David Laight
2017-02-07 14:52                     ` Petko Manolov
     [not found] ` <20170204165451.GU3442-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
2017-02-04 16:56   ` [PATCH net 3/4] catc: Combine failure cleanup code in catc_probe() Ben Hutchings
2017-02-04 16:57 ` [PATCH net 4/4] catc: Use heap buffer for memory size test Ben Hutchings
2017-02-07 15:07 ` [PATCH net 0/4] Fix on-stack USB buffers 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=20170206132124.GA3038@localhost \
    --to=johan@kernel.org \
    --cc=ben@decadent.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=lisandro@debian.org \
    --cc=netdev@vger.kernel.org \
    --cc=petkan@nucleusys.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).