netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: yevgenyp@mellanox.co.il
Cc: jeff@garzik.org, rdreier@cisco.com, netdev@vger.kernel.org
Subject: Re: [PATCH 9/9 V2] mlx4_en: Multiqueue support
Date: Mon, 29 Dec 2008 18:41:09 -0800 (PST)	[thread overview]
Message-ID: <20081229.184109.77843771.davem@davemloft.net> (raw)
In-Reply-To: <49589EF5.8070800@mellanox.co.il>

From: Yevgeny Petrilin <yevgenyp@mellanox.co.il>
Date: Mon, 29 Dec 2008 11:57:09 +0200

> Added a function that performs hashing on the TX traffic.
> The hashing is only done for TCP or UDP packets, all other packets
> are sent to a default queue.
> We use an indirection table with an entry for each hash result.
> For each entry in the table, we hold statistics regarding the stream
> that corresponds to that entry. Packets are then directed to a TX queue
> according to stream's pattern.
> A ring is opened for each queue.
> 
> Signed-off-by: Yevgeny Petrilin <yevgenyp@mellanox.co.il>

You are not supposed to provide a driver private function
to hash the traffic.

The generic code already hashes traffic for you, and whatever
it doesn't handle currently will be handled in the future.
The generic code is where gaps should be filled in.

The override function pointer is only for wireless which has
special needs in queue selection that have nothing to do with
flow seperation.

Please resubmit this without your private hashing function.

Thank you.

  reply	other threads:[~2008-12-30  2:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29  9:57 [PATCH 9/9 V2] mlx4_en: Multiqueue support Yevgeny Petrilin
2008-12-30  2:41 ` David Miller [this message]
2008-12-30 16:54   ` Yevgeny Petrilin
2008-12-30 19:54     ` 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=20081229.184109.77843771.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdreier@cisco.com \
    --cc=yevgenyp@mellanox.co.il \
    /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).