From: Greg Banks <gnb@sgi.com>
To: Eric Whiting <ewhiting@amis.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: Re: [PATCH] resend: knfsd multiple UDP sockets
Date: Wed, 2 Jun 2004 10:47:45 +1000 [thread overview]
Message-ID: <20040602004745.GA32206@sgi.com> (raw)
In-Reply-To: <40BCAD5F.4DE90B76@amis.com>
On Tue, Jun 01, 2004 at 10:22:55AM -0600, Eric Whiting wrote:
> Neil Brown wrote:
> >
> > I have two concerns, that can possibly be allayed.
> >
> > Firstly, the reply to any request is going to go out the socket that
> > the request came in on. However some network configurations can have
> > requests arrive on one interface that need to be replied to on a
> > different interface(*).
>
> Neil,
>
> Some misc data: It is my understanding that 'networkappliance data ontap' is
> wired up to send replies out the same interface the request came in on. This
> solves some problems of managing systems connected via multiple network paths.
> I realize it might also create other problems..
Linux is a general purpose OS where users have the expecation that
networking behaves in certain ways. ONTAP drives an appliance whose
purpose is to run file sharing protocols. This means they can make
network level compromises and optimisations that we can't.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
next prev parent reply other threads:[~2004-06-02 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 4:20 [PATCH] resend: knfsd multiple UDP sockets Greg Banks
2004-05-28 5:14 ` Neil Brown
2004-05-28 7:42 ` Greg Banks
2004-06-01 16:22 ` Eric Whiting
2004-06-01 23:19 ` Neil Brown
2004-06-02 0:47 ` Greg Banks [this message]
2004-06-08 1:15 ` Greg Banks
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=20040602004745.GA32206@sgi.com \
--to=gnb@sgi.com \
--cc=ewhiting@amis.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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.