From: "Michał Mirosław" <mirqus-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Oliver Neukum <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
Cc: Alan Stern
<stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>,
David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
shemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org,
tom.leiming-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: future developments of usbnet
Date: Sat, 14 May 2011 12:46:09 +0200 [thread overview]
Message-ID: <BANLkTik7s2LG+-ow414VGLALFmk_fEngNQ@mail.gmail.com> (raw)
In-Reply-To: <201105141201.40265.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2011/5/14 Oliver Neukum <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>:
> Am Donnerstag, 12. Mai 2011, 16:37:28 schrieb Alan Stern:
>> Therefore usbnet's poll routine should take the "weight" argument as an
>> indication of how many outstanding rx URBs are allowed. Each time the
>> poll routine is called, it should check to see if any rx URBs have
>> completed since the previous poll. If not then there is no network
>> traffic, so usbnet can take itself out of the poll loop. Otherwise,
>> the number of outstanding URBs should be adjusted (by unlinking some or
>> submitting more -- subject to some fixed maximum limit) to match the
>> new "weight".
> What does happen if we reach the weight 0 ?
Poll callback won't be called with weight 0. If there are more RX
packets after processing 'weight' of them, then the callback will be
called again later.
Best Regards,
Michał Mirosław
--
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
next prev parent reply other threads:[~2011-05-14 10:46 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
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 [this message]
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=BANLkTik7s2LG+-ow414VGLALFmk_fEngNQ@mail.gmail.com \
--to=mirqus-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org \
--cc=shemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org \
--cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org \
--cc=tom.leiming-Re5JQEeQqe8AvxtiuMwx3w@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).