On Thu, Jan 09, 2014 at 04:28:49PM +0800, Jason Wang wrote:
> On 01/08/2014 10:40 PM, Neil Horman wrote:
> > On Wed, Jan 08, 2014 at 11:21:21AM +0800, Jason Wang wrote:
> >> On 01/07/2014 09:17 PM, Neil Horman wrote:
> >>> On Tue, Jan 07, 2014 at 11:42:24AM +0800, Jason Wang wrote:
> On
On 01/08/2014 10:40 PM, Neil Horman wrote:
> On Wed, Jan 08, 2014 at 11:21:21AM +0800, Jason Wang wrote:
>> On 01/07/2014 09:17 PM, Neil Horman wrote:
>>> On Tue, Jan 07, 2014 at 11:42:24AM +0800, Jason Wang wrote:
On 01/06/2014 08:42 PM, Neil Horman wrote:
> On Mon, Jan 06, 2014 at
On 01/08/2014 10:40 PM, Neil Horman wrote:
On Wed, Jan 08, 2014 at 11:21:21AM +0800, Jason Wang wrote:
On 01/07/2014 09:17 PM, Neil Horman wrote:
On Tue, Jan 07, 2014 at 11:42:24AM +0800, Jason Wang wrote:
On 01/06/2014 08:42 PM, Neil Horman wrote:
On Mon, Jan 06, 2014 at 11:21:07AM +0800,
On Thu, Jan 09, 2014 at 04:28:49PM +0800, Jason Wang wrote:
On 01/08/2014 10:40 PM, Neil Horman wrote:
On Wed, Jan 08, 2014 at 11:21:21AM +0800, Jason Wang wrote:
On 01/07/2014 09:17 PM, Neil Horman wrote:
On Tue, Jan 07, 2014 at 11:42:24AM +0800, Jason Wang wrote:
On 01/06/2014 08:42 PM,
On Wed, Jan 08, 2014 at 11:21:21AM +0800, Jason Wang wrote:
> On 01/07/2014 09:17 PM, Neil Horman wrote:
> > On Tue, Jan 07, 2014 at 11:42:24AM +0800, Jason Wang wrote:
> >> On 01/06/2014 08:42 PM, Neil Horman wrote:
> >>> On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
>
On Wed, Jan 08, 2014 at 11:21:21AM +0800, Jason Wang wrote:
On 01/07/2014 09:17 PM, Neil Horman wrote:
On Tue, Jan 07, 2014 at 11:42:24AM +0800, Jason Wang wrote:
On 01/06/2014 08:42 PM, Neil Horman wrote:
On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
Currently, the tx queue
On 01/07/2014 09:17 PM, Neil Horman wrote:
> On Tue, Jan 07, 2014 at 11:42:24AM +0800, Jason Wang wrote:
>> On 01/06/2014 08:42 PM, Neil Horman wrote:
>>> On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit().
On Tue, Jan 07, 2014 at 11:42:24AM +0800, Jason Wang wrote:
> On 01/06/2014 08:42 PM, Neil Horman wrote:
> > On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
> >> Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit().
> >> The
> >> will cause several issues:
> >>
>
[...]
+int dfwd_direct_xmit(struct sk_buff *skb, struct net_device *dev,
+ void *accel_priv)
+{
+struct netdev_queue *txq;
+int ret = NETDEV_TX_BUSY;
+int index;
+
+BUG_ON(!dev->netdev_ops->ndo_dfwd_select_queue);
+index =
On 1/5/2014 7:21 PM, Jason Wang wrote:
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit(). The
will cause several issues:
- NETIF_F_LLTX was forced for macvlan device in this case which lead extra lock
contention.
- dev_hard_start_xmit() was called with NULL txq which
On 1/5/2014 7:21 PM, Jason Wang wrote:
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit(). The
will cause several issues:
- NETIF_F_LLTX was forced for macvlan device in this case which lead extra lock
contention.
- dev_hard_start_xmit() was called with NULL txq which
[...]
+int dfwd_direct_xmit(struct sk_buff *skb, struct net_device *dev,
+ void *accel_priv)
+{
+struct netdev_queue *txq;
+int ret = NETDEV_TX_BUSY;
+int index;
+
+BUG_ON(!dev-netdev_ops-ndo_dfwd_select_queue);
+index =
On Tue, Jan 07, 2014 at 11:42:24AM +0800, Jason Wang wrote:
On 01/06/2014 08:42 PM, Neil Horman wrote:
On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit().
The
will cause several issues:
- NETIF_F_LLTX
On 01/07/2014 09:17 PM, Neil Horman wrote:
On Tue, Jan 07, 2014 at 11:42:24AM +0800, Jason Wang wrote:
On 01/06/2014 08:42 PM, Neil Horman wrote:
On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit().
The
will
On 01/06/2014 08:42 PM, Neil Horman wrote:
> On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
>> Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit().
>> The
>> will cause several issues:
>>
>> - NETIF_F_LLTX was forced for macvlan device in this case which lead
On Mon, Jan 06, 2014 at 07:06:25AM -0800, John Fastabend wrote:
> On 01/06/2014 04:42 AM, Neil Horman wrote:
> >On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
> >>Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit().
> >>The
> >>will cause several issues:
> >>
>
On 01/06/2014 04:42 AM, Neil Horman wrote:
On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit(). The
will cause several issues:
- NETIF_F_LLTX was forced for macvlan device in this case which lead extra lock
On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
> Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit(). The
> will cause several issues:
>
> - NETIF_F_LLTX was forced for macvlan device in this case which lead extra
> lock
> contention.
> -
On Mon, 2014-01-06 at 11:21 +0800, Jason Wang wrote:
> Currently, the tx queue were selected implicitly in
> ndo_dfwd_start_xmit(). The
> will cause several issues:
>
> - NETIF_F_LLTX was forced for macvlan device in this case which lead
> extra lock
> contention.
> - dev_hard_start_xmit() was
On Mon, 2014-01-06 at 11:21 +0800, Jason Wang wrote:
Currently, the tx queue were selected implicitly in
ndo_dfwd_start_xmit(). The
will cause several issues:
- NETIF_F_LLTX was forced for macvlan device in this case which lead
extra lock
contention.
- dev_hard_start_xmit() was called
On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit(). The
will cause several issues:
- NETIF_F_LLTX was forced for macvlan device in this case which lead extra
lock
contention.
- dev_hard_start_xmit() was
On 01/06/2014 04:42 AM, Neil Horman wrote:
On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit(). The
will cause several issues:
- NETIF_F_LLTX was forced for macvlan device in this case which lead extra lock
On Mon, Jan 06, 2014 at 07:06:25AM -0800, John Fastabend wrote:
On 01/06/2014 04:42 AM, Neil Horman wrote:
On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit().
The
will cause several issues:
- NETIF_F_LLTX
On 01/06/2014 08:42 PM, Neil Horman wrote:
On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit().
The
will cause several issues:
- NETIF_F_LLTX was forced for macvlan device in this case which lead extra
lock
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit(). The
will cause several issues:
- NETIF_F_LLTX was forced for macvlan device in this case which lead extra lock
contention.
- dev_hard_start_xmit() was called with NULL txq which bypasses the net device
watchdog
-
Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit(). The
will cause several issues:
- NETIF_F_LLTX was forced for macvlan device in this case which lead extra lock
contention.
- dev_hard_start_xmit() was called with NULL txq which bypasses the net device
watchdog
-
26 matches
Mail list logo
