mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Chacko <peterchacko35@gmail.com>
To: Gallus <gall.cwpl@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Kernel hard_start_xmit performance vs SOCK_RAW performance
Date: Fri, 26 Jun 2009 20:17:57 +0530	[thread overview]
Message-ID: <1f808b4a0906260747i610b68bej2eaeb87d72e24c08@mail.gmail.com> (raw)
In-Reply-To: <b08bcbf50906260735q6af6522dl6f1bb407f68a801e@mail.gmail.com>

Did you try using PACKET socket interface  from your module  ?
(essentially as fast as hard-start-transmit() path ...there will be
tools that can be used for this purpose....I am not sure of any such
tool though...:-) you need to skip the scheduling (qdiscs) path also..

I think, Linux-net mailing list would be more appropriate to have this
discussion.

Thanks,
Peter

NetDiox computing systems
Bangalore-india
www.netdiox.com
080 2664 0708

On Fri, Jun 26, 2009 at 8:05 PM, Gallus<gall.cwpl@gmail.com> wrote:
> 2009/6/26 Alan Cox <alan@lxorguk.ukuu.org.uk>:
>> On Fri, 26 Jun 2009 16:04:04 +0200
>> Gallus <gall.cwpl@gmail.com> wrote:
>>
>>> Hi,
>>> what path would you choose to rapidly generate packets
>>
>> Documentation/networking/pktgen.txt
>
> Thank you Alan for the answer.
>
> However, my goal is to generate packets with certain *content* in them.
>
> --
> Regards,
> Gallus
> please CC me
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

      reply	other threads:[~2009-06-26 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 14:04 Gallus
2009-06-26 14:08 ` Alan Cox
2009-06-26 14:35   ` Gallus
2009-06-26 14:47     ` Peter Chacko [this message]

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=1f808b4a0906260747i610b68bej2eaeb87d72e24c08@mail.gmail.com \
    --to=peterchacko35@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gall.cwpl@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®