public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Petko Manolov <petkan@nucleusys.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: Greg KH <greg@kroah.com>, Ben Hutchings <ben@decadent.org.uk>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH net 2/4] rtl8150: Use heap buffers for all register access
Date: Tue, 7 Feb 2017 16:52:44 +0200	[thread overview]
Message-ID: <20170207145244.ff5uffxb66wyezqz@p310> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DB027DD9F@AcuExch.aculab.com>

On 17-02-07 14:14:30, David Laight wrote:
> From: Petko Manolov
> > Sent: 07 February 2017 13:21
> ...
> > > > Would you consider what David proposed (usb_control_msg_with_malloc()) for 4.11,
> > > > for example?  I for one will use something like that in all my drivers.
> > >
> > > Sure, but you might want to make it a bit smaller of a function name :)
> > 
> > Whatever i say may be taken as volunteering. :D
> > 
> > Second - i've got really bad taste when naming things.  asdfgl() is a short name
> > although not very descriptive. ;)
> ...
> 
> Actually, for short control transfers a field in the urb itself could be used 
> (unless another 8 bytes makes the structure larger).
> 
> IIRC for xhci, the 8 byte pointer field can be marked as containing the actual 
> data - saving the hardware from doing another dma as well.

Unless set up for automatic triggering, 8 byte DMA transfer is an overkill (by 
means of having to program a bunch of IO registers), especially on a 64bit 
machine.

However, not knowing the USB host controllers specifics i'll shut up.


cheers,
Petko

  reply	other threads:[~2017-02-07 14:53 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
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 [this message]
     [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=20170207145244.ff5uffxb66wyezqz@p310 \
    --to=petkan@nucleusys.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=ben@decadent.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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