All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
Cc: "linux-rdma
	(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RE: [RFC] [PATCH 0/4] librdmacm: Rsockets API and implementation
Date: Wed, 11 Apr 2012 21:44:23 +0000	[thread overview]
Message-ID: <1828884A29C6694DAF28B7E6B8A82373451ACF9C@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <4F85E720.5040307-HInyCGIudOg@public.gmane.org>

> Interesting work. Regarding direct data placement: have the io_submit()
> and io_getevents() system calls been considered ? Those are the
> foundation of libaio.

I did look at aio and other interfaces, but I didn't try to move beyond the idea phase.  With aio, I didn't see how the calls could easily be used by a socket app without recoding, or even redesigning the app around the aio interface.

Are you suggesting calls similar to io_submit() and io_getevents() that work with a socket rather than an aio_context_t?

My intent is to start a more general discussion on whether direct data placement is needed (I'm assuming yes) and the best way to add it.  I wasn't comfortable enough with just my own musing on things to dedicate any time implementing something.

- Sean
--
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-04-11 21:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 18:29 [RFC] [PATCH 0/4] librdmacm: Rsockets API and implementation Hefty, Sean
     [not found] ` <1828884A29C6694DAF28B7E6B8A82373451ACEEF-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-04-11 20:18   ` Bart Van Assche
     [not found]     ` <4F85E720.5040307-HInyCGIudOg@public.gmane.org>
2012-04-11 21:44       ` Hefty, Sean [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=1828884A29C6694DAF28B7E6B8A82373451ACF9C@ORSMSX101.amr.corp.intel.com \
    --to=sean.hefty-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=bvanassche-HInyCGIudOg@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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.