All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pradeep Satyanarayana <pradeeps-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Sridhar Samudrala <sri-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
	"Hefty,
	Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	kashyapv-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org,
	Shlomo Pongratz <shlomop-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: rsockets and other performance
Date: Sun, 17 Jun 2012 14:20:39 -0700	[thread overview]
Message-ID: <4FDE4A27.5080601@linux.vnet.ibm.com> (raw)
In-Reply-To: <4FDD85B3.2090406-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

On 06/17/2012 12:22 AM, Or Gerlitz wrote:
> On 6/14/2012 7:09 PM, Sridhar Samudrala wrote:
>> Enabling NETIF_F_SG improves the throughput further by avoiding a 
>> additional kernel memcpy caused by skb_linearize() in dev_queue_xmit().
>
> Hi Sridhar,
>
> If you **only** enable NETIF_F_SG for CM, does this yields any gain? 
> did you had to patch the code for that end?
>
Hi Or, We did not try only NETIF_F_SG for IPoIB CM. We tried it along 
with NETIF_F_IP_CSUM. We did run
into issues  with netperf i.e. netperf errors out  along with 
NETIF_F_SG. However, iperf worked fine. Did not investigate that further.

Thanks
Pradeep


--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" 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:[~2012-06-17 21:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 15:24 rsockets and other performance Pradeep Satyanarayana
     [not found] ` <4FDA0233.6090409-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2012-06-14 16:02   ` Hefty, Sean
2012-06-14 16:09   ` Sridhar Samudrala
     [not found]     ` <1339690194.14317.5.camel-5vSEHtyIv2TJ4MwkZ4db91aTQe2KTcn/@public.gmane.org>
2012-06-17  7:22       ` Or Gerlitz
     [not found]         ` <4FDD85B3.2090406-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-06-17 21:20           ` Pradeep Satyanarayana [this message]
2012-06-14 17:22   ` Jason Gunthorpe
     [not found]     ` <20120614172245.GC6552-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-06-15  6:48       ` Vivek Kashyap
     [not found]         ` <alpine.LRH.2.00.1206142336220.13728-Nzfcc2Us4m+Xfo/+vza+31aTQe2KTcn/@public.gmane.org>
2012-06-15 17:19           ` Jason Gunthorpe
     [not found]             ` <20120615171919.GA17224-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-06-18  6:37               ` Vivek Kashyap
     [not found]                 ` <alpine.LRH.2.00.1206172330220.13728-Nzfcc2Us4m+Xfo/+vza+31aTQe2KTcn/@public.gmane.org>
2012-06-18 17:53                   ` Jason Gunthorpe

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=4FDE4A27.5080601@linux.vnet.ibm.com \
    --to=pradeeps-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=kashyapv-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=shlomop-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=sri-r/Jw6+rmf7HQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.