netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Lei <tom.leiming-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Oliver Neukum <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: future developments of usbnet
Date: Mon, 9 May 2011 11:26:04 +0800	[thread overview]
Message-ID: <BANLkTimXmHr8aJ7WgRVvZj85t-gw68C_Ww@mail.gmail.com> (raw)
In-Reply-To: <201105062045.37336.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>

Hi,

2011/5/7 Oliver Neukum <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>:
> Hi,
>
> I'd like to get a feeling what people are working out there regarding usbnet.
> So please, if you do something, or think something ought to be done, please
> speak up now.
>
> IMHO usbnet needs better support for
>
> - batching protocols
> - double buffering on the rx path
>
> with the latter having higher priority.
>
> Coments?

Maybe another thing about rx should be considered too: we should introduce
one flow control mechanism into rx path so that too much coming packets can
not consume many of memory and cause out of memory for atomic allocation.

Current implementation has such kind of risk certainly, as i explained in the
patch with title below:

       usbnet: runtime pm: fix out of memory

thanks,
-- 
Ming Lei
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-05-09  3:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 18:45 future developments of usbnet Oliver Neukum
     [not found] ` <201105062045.37336.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2011-05-09  3:26   ` Ming Lei [this message]
2011-05-09  8:42     ` Oliver Neukum
     [not found]       ` <201105091042.01014.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2011-05-09 15:22         ` Ming Lei
2011-05-09 15:31           ` Alan Stern
2011-05-09 15:46             ` Stephen Hemminger
2011-05-11 17:37               ` Oliver Neukum
     [not found]                 ` <201105111937.47448.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2011-05-11 17:47                   ` David Miller
2011-05-12  7:59                     ` Oliver Neukum
     [not found]                       ` <201105120959.28473.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2011-05-12 14:37                         ` Alan Stern
2011-05-14 10:01                           ` Oliver Neukum
     [not found]                             ` <201105141201.40265.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2011-05-14 10:46                               ` Michał Mirosław
2011-05-12 17:46                         ` David Miller
2011-05-10  9:42   ` Richard Cochran

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=BANLkTimXmHr8aJ7WgRVvZj85t-gw68C_Ww@mail.gmail.com \
    --to=tom.leiming-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).